-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add ability to handle Split metrics #38402
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
Comments
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 |
/label processor/schema |
Pinging code owners for processor/schema: @MovieStoreGuy @ankitpatel96 @dineshg13. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label. |
/label -needs-triage waiting-for-code-owners priority:p2 |
Component(s)
processor/schema
Is your feature request related to a problem? Please describe.
Split Metrics were introduced as part of schema file format 1.1.0 .
see https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/schemas/file_format_v1.1.0.md
Schema Processor currently doesn't support Split Metrics operation.
Describe the solution you'd like
Schema Processor should be able to handle Split Metrics.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: