yzhang2017's Posts

Reading further, the pricing appears to be calculated as  `price = write_per_sec_at_95_percentile * num_datapoints`. So, despite the storage of data is free and the new datapoints don't as many w... See more...
Reading further, the pricing appears to be calculated as  `price = write_per_sec_at_95_percentile * num_datapoints`. So, despite the storage of data is free and the new datapoints don't as many write, the pricing will still be the top write_per_sec from the other part. Plus the addition of the new datapoints, the cost would increase drastically. So, it appears not to be a good idea to implement in this way as for higher cost.
I am think of of using wavefront as a key-value store for counters, as it is easily available as charts. However, it would introduce many new keys. I am thinking it might require to delete tho... See more...
I am think of of using wavefront as a key-value store for counters, as it is easily available as charts. However, it would introduce many new keys. I am thinking it might require to delete those keys periodically. For statsD, to delete an existing key, I could just delete the corresponding whisper directory. Is this possible to do in wavefront? If so, which wavefront API can do this work? Or, is introducing new keys (say 2000 per day) not a problem, and they don't need to be deleted? (I read about the pricing, it only charges by rate of writing: https://www.wavefront.com/pricing/ )
We are configuring alerts on wavefront for multiple environments, and repeating ourselves by creating / cloning multiple alerts and make adjustments. It is difficult to make changes as there are ... See more...
We are configuring alerts on wavefront for multiple environments, and repeating ourselves by creating / cloning multiple alerts and make adjustments. It is difficult to make changes as there are many alerts to modify. Is there a way to pass parameter to alert configuration to avoid this redundancy in alert?