You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In certain cases it would be very useful to have the same control over the collectors own telemetry (mainly metrics) as we do over other OTEL data points. For example, I'd like to be able to modify the aggregation temporality for the metrics as it seems by default they are all cumulative, and for certain metrics like refused spans/metrics delta seems a more intuitive value. It would also be convenient to be able to enable/disable specific metrics the same way that we are able to in other components.
Describe the solution you'd like
I would like to the service telemetry config to allow for configuration of telemetry data
Describe alternatives you've considered
Using the filter processor to exclude specific metrics, create queries on backend to extract delta.
Additional context
I'm aware this is not critical with the impending GA release, but wanted to bring it up as an eventual enhancement
The text was updated successfully, but these errors were encountered:
Hello @akats7! Yes I'm currently working on supporting additional configuration for the Collector as part of #7532. I've started making metrics more configurable using the scheme defined by the configuration working group and would love more help to add additional feature support!
Let me know if this is something you'd like to help with, tackling configuring views was next on my list of priorities.
Is your feature request related to a problem? Please describe.
In certain cases it would be very useful to have the same control over the collectors own telemetry (mainly metrics) as we do over other OTEL data points. For example, I'd like to be able to modify the aggregation temporality for the metrics as it seems by default they are all cumulative, and for certain metrics like refused spans/metrics delta seems a more intuitive value. It would also be convenient to be able to enable/disable specific metrics the same way that we are able to in other components.
Describe the solution you'd like
I would like to the service telemetry config to allow for configuration of telemetry data
Describe alternatives you've considered
Using the filter processor to exclude specific metrics, create queries on backend to extract delta.
Additional context
I'm aware this is not critical with the impending GA release, but wanted to bring it up as an eventual enhancement
The text was updated successfully, but these errors were encountered: