On Tuesday, 4 January 2022 at 09:34:41 UTC Victor Sudakov wrote: > You probably meant "comprise" ?
Yes. Disconnect between brain and keyboard! > I've noticed that if I take a larger resampling interval, like > "foo[2d:1h]", I lose all my peaks. Which is kind of understandable now > but the question "how to better find peaks" kind of remains. (foo == N)[2d:15s] will find the peaks, with approximate timestamps within 15 seconds of the actual time the data was sampled. If you want, you can then hit the API with additional queries foo[15s] @timestamp to get the raw metrics with exact timestamps (it will return the raw timeseries between timestamp-15s and timestamp). But in many applications, you don't care about this. You're only sampling the data every 15 seconds anyway, which means you'll miss the exact time when the state of the thing you're sampling changed; in other words, the timestamp will already have between 0 and 15 seconds of error. So adding another 0-15 seconds of error is probably not a big deal. -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/2b12438c-29c8-4e76-bb51-7b4bcfb21703n%40googlegroups.com.
