Metrics not reset (accumulating)

[noxdafox]

Metrics not reset (accumulating)

[webmozart]

Thanks for your answer and for the plugin!

[webmozart]

I think I found the culprint: In

rabbitmq-cloudwatch-exporter/lib/rabbitmq_cloudwatch_exporter/overview_metrics.ex

Line 27 in 274cef6

RabbitMGMTDB.get_overview(Common.no_range)

and other similar pieces of code, Common.no_range is passed as range parameter, which as a result returns the metric since startup. Does anybody find that useful?

It would be great if we could either pass a range, or if the range was even preconfigured to cloudwatch_exporter.export_period. The latter would make most sense IMO, as any aggregation can then be done in CloudWatch on top of that (e.g. total messages published in the last two weeks etc.).

I might try myself at a PR, but I have no Erlang skills unfortunately.

[webmozart]

Alright I found the answer. In CloudWatch metrics math, there's a RATE() function which returns exactly the desired values.

[noxdafox]

The plugin collects the metrics raw from the broker internal metrics storage and uploads them as they are.

It does not apply any transformation. The Management plugin collects the same metrics but transforms them according to the needs of representation.

It is responsibility of the user to decide how to represent the metrics as such. Reason for this is that applying transformations to metrics often reduces their resolution or hides some information.

Most of the dashboard technologies (Graphana, Chronograph, CW, ...) allow to set how to represent information. In your case, what you need is the derivative over time of the Publish value.

Glad you sorted your need.