How to aggregate Cinnamon rates over time
Cinnamon does not support this natively in part because neither of our underlying metric backends support that type of rate metric*. The Rate metric is for rates of occurrences, like how many times has this happened, and the Recorder is for measuring distributions of values, like the time it takes for a certain operation to be performed.
If you want to aggregate your values and only output one value that represents a total for a certain time unit, you should use a Gauge, and in this case a GaugeLong. You need to do the aggregation yourself on the side, and then set the Gauge when you have computed the combined value.
* Also the the rate metric is for recording the rate for actual points in time where things happen, and updating of the rate metric with the values that you read yourself might not align properly (in time) with each other, leading to skewed values in the weighted moving averages that the rate metric reports.
What are the units for Cinnamon rates?
The units will actually depend on the metric backend used. Rate is a general interface that just has a mark method. For the Coda Hale Metrics backend, the custom metrics Rate is backed by a Meter. Meters record rates in events per second. These ...
Why should I use Telemetry (Cinnamon) instead of Kamon?
Telemetry (aka Cinnamon) is the industry’s most capable tool for the monitoring of Akka, Play and Lagom applications. While Cinnamon and Kamon share some common features such as actor mailbox metrics, dead letter message counts and fine-grained ...
Why can't I see Cinnamon metrics when running my Play application in development?
A common cause for Cinnamon metrics not being reported in Play development is because Cinnamon does not currently support Play’s development mode*, which is the mode used by the Play server when started using the sbt run command. As a workaround, ...
How to monitor my Play application? Can I use Cinnamon?
Yes! Starting in version 2.7 Cinnamon added support for monitoring Play 2.6+ applications. For more information, you can check out the announcement here.
Split Brain Resolver throws java.lang.NoSuchMethodError
This error happens when using SBR 1.1.4 in conjunction with Lightbend Telemetry (aka Cinnamon) 2.10.8. The changes introduced in SBR, unfortunately, broke the instrumentation in Cinnamon. That has been corrected in Cinnamon version 2.10.9 and the ...