[connector/exceptions] Relate generated metrics from the source trace/span #24409
Comments
marctc
added
enhancement
|
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Removing |
|
@marctc Would you be interested in being a code owner for this component, seeing as you're the main contributor here? It would be great to get some more help on this if you have the availability! |
Yes, definitely. But I think I have to be maintainer, first right? In any case, I'm interested in both. Thanks! |
|
You just have to be a member. The directions for joining are there, it looks like you should meet them without a problem 👍 Once you're a member you can open a PR to add yourself as a code owner here. |
@marctc is the original component proposer and author, and is now a [member of the OpenTelemetry community](open-telemetry/community#1761). He also [expressed interest in being a code owner](#24409 (comment)) when I asked.
…ry#29692) @marctc is the original component proposer and author, and is now a [member of the OpenTelemetry community](open-telemetry/community#1761). He also [expressed interest in being a code owner](open-telemetry#24409 (comment)) when I asked.
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
…or (#31819) **Description:** <Describe what has changed.> Adds support for exemplars fort the generated metrics from exceptions. It relates the span and trace id with metrics. The ingestion needs to be enabled via config (disbled by default). **Link to tracking Issue:** Resolves #24409 **Documentation:** Added documentation for enabling generation of exemplars. --------- Co-authored-by: Juraci Paixão Kröhling <[email protected]>
…or (open-telemetry#31819) **Description:** <Describe what has changed.> Adds support for exemplars fort the generated metrics from exceptions. It relates the span and trace id with metrics. The ingestion needs to be enabled via config (disbled by default). **Link to tracking Issue:** Resolves open-telemetry#24409 **Documentation:** Added documentation for enabling generation of exemplars. --------- Co-authored-by: Juraci Paixão Kröhling <[email protected]>
Component(s)
No response
Is your feature request related to a problem? Please describe.
The current implementation generates metrics from recorded exceptions in spans, but is not possible to see which traces and spans generated those metrics.
Describe the solution you'd like
It would be useful to correlate spans to generated metrics, specially for debugging purpouse during outages. Using exemplars with the generated metrics would this make work.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: