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
Is there a prefix or standards for application level attributes?
As in Elastic Common Schema, are there prefixes like fields., labels. to allow to put free attributes
As exemple, how named a attributes like application code or application name ?
The text was updated successfully, but these errors were encountered:
It's not official per spec, but in the OTel demo -- which is intended to be a canonical implementation -- the app. prefix is used for attributes within an application, like so: https://github.com/open-telemetry/opentelemetry-demo/blob/7543c595d9e43cda0433bf8461940022152f302f/src/quote/app/routes.php#L32
app.
Sorry, something went wrong.
No branches or pull requests
Is there a prefix or standards for application level attributes?
As in Elastic Common Schema, are there prefixes like fields., labels. to allow to put free attributes
As exemple, how named a attributes like application code or application name ?
The text was updated successfully, but these errors were encountered: