We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I checked the history of increasing from 63 to 255.
Could consider the situation of using more than 255 instrument names?
open-telemetry/opentelemetry-java#5697
Unlimited, but I wish I could specify the settings.
Thanks to so many people, I'm using good functions well.
We have installed an openelemetry java agent in our service to use openelemetry and opensearchapm.
I got caught in instrument-name limit (255) causing WARN. Is there a plan to change the limit?
No response
The text was updated successfully, but these errors were encountered:
This is not the correct repository for this request. Metric name length is defined in the specification https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#instrument-name-syntax and enforced by the opentelemetry java sdk implemented in https://github.com/open-telemetry/opentelemetry-java
Sorry, something went wrong.
Thank you for your kind
No branches or pull requests
Is your feature request related to a problem? Please describe.
I checked the history of increasing from 63 to 255.
Could consider the situation of using more than 255 instrument names?
open-telemetry/opentelemetry-java#5697
Describe the solution you'd like
Unlimited, but I wish I could specify the settings.
Describe alternatives you've considered
Thanks to so many people, I'm using good functions well.
We have installed an openelemetry java agent in our service to use openelemetry and opensearchapm.
I got caught in instrument-name limit (255) causing WARN. Is there a plan to change the limit?
Additional context
No response
The text was updated successfully, but these errors were encountered: