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
The current version of opentelemetry-instrumentation-http has a limitation where it removes attributes from outgoing-request and incoming-request metrics due to high cardinality issues. However, it would be useful to have the capability of adding other attributes to the HTTP metrics according to the user's requirements. For instance, if I want to filter and monitor specific downstream requests, adding http_target to the outgoing-request metric does not create high cardinality issues for me or other attributes e.g http_status_family: 2xx
Options would be by passing metricAttributes into applyCustomAttributesOnSpan
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The current version of
opentelemetry-instrumentation-http
has a limitation where it removes attributes fromoutgoing-request
andincoming-request
metrics due to high cardinality issues. However, it would be useful to have the capability of adding other attributes to the HTTP metrics according to the user's requirements. For instance, if I want to filter and monitor specific downstream requests, addinghttp_target
to theoutgoing-request
metric does not create high cardinality issues for me or other attributes e.ghttp_status_family: 2xx
Options would be by passing
metricAttributes
intoapplyCustomAttributesOnSpan
cc: @hectorhdzg @legendecas for opinions and feedback 😊
Thank you 🙏
Beta Was this translation helpful? Give feedback.
All reactions