-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable the spanmetrics
connector component.
#18760
Comments
Pinging code owners for connector/spanmetrics: @albertteoh. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for processor/spanmetrics: @albertteoh. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
spanmetrics
connector component.spanmetrics
connector component.
Thanks for writing this up @kovrus. Sounds like a good plan, for both before and after enabling the connector. |
Component(s)
connector/spanmetrics
Describe the issue you're reporting
The
spanmetrics
connector is a port of thespanmetrics
processor, but since it is going to be a new component, we thought that it can be a good time to fix some issues of the formerspanmetrics
processor in the new connector and bring the connector closer to the OTel spec, drop any related Prometheus specific conventions that the processor heavily uses, etc.We can deprecate the processor and keep both components for some time to give users time to migrate. It should not be that critical anyways because the
spanmetrics
processor's stability level isin development
.TODO when enabling the component:
spanmetrics
processor to thespanmetrics
connectoroperation
attribute tospan.name
#18529_total
from generated metrics names. #18677spanmetrics
processorThe text was updated successfully, but these errors were encountered: