Counters must only increase. Any reduction is seen as a counter reset. If this isn't a counter use the derivative function rather than rate
On 26 February 2020 14:05:31 GMT, Venkata Bhagavatula <[email protected]> wrote: >Hi, > >In our application, there is one metric that we are deriving from >another >metric using recording rules. >When we plot the graphs of recording metric and the original metric in >grafana, we see the graph to follow the same trend. But when we applied >increase , then we have seen recording metric is having huge spikes, >whereas original metric is not having these spikes. > >following is the plotted graph: >[image: image.png] >The bottom panels show the increase of both these metrics over time. >As >you can see, there are points where the metric values goes down. >Prometheus >handles these as resets for metric type “Counter”, and the increase >function handles it gracefully. > >Can you let us know how these recording metrics are treated in >prometheus? >and any pointers on how to debug this issue. > >Thanks n Regards, >Chalapathi. > >-- >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/CABXnQPsEbyNjxzVH267NURtZNGwy7LZGcBueWzhYdgtaS_F6pQ%40mail.gmail.com. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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/9A9C2A34-80E4-40E1-9ACD-5C722A0B05D8%40Jahingo.com.
