Replies: 1 comment
-
Hello That does not seem like a bad solution at all. There are many custom "configurations" that anyone can need for their exporters and using a subclass is a clean way of achieving that. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
i asked the same question around 3 months ago on stackoverflow but never received an answer. I think this is an interesting usecase and i am still looking for a proper way to do it so i try my luck here:
I am exporting some counter metrics (message counts per device) to Azure Monitor (however i think this question must be answered independent from chosen export).
I count messages with different attributes (e.g. name of device which sent the message) and export the metrics periodically. I am using Delta temporality. Since the devices sometimes send messages and sometimes not, the counter is often zero for a attribute set. Currently the metrics are exported always for all attribute sets, even for the ones where the counter is zero.
which results in the following output
I want to achieve that the metrics are only exported (or collected) if the counter for an attribute set is larger than zero.
Currently i am using a very ugly way that i subclass the exporter and ignore points where the value is 0, but i would like to know what's the recommended way to achieve this behaviour.
Beta Was this translation helpful? Give feedback.
All reactions