Concept example for semantic conventions registry inside of an integration #14343
+16
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…an up registry - Updated all registry files to use OpenTelemetry semantic conventions v1.34.0 - Fixed registry_manifest.yaml to follow proper Weaver format with metadata and dependencies - Removed custom groups from registry.yaml, keeping only imports for pure standards compliance - Updated documentation to reflect import-only approach and latest OTel version
💔 Build Failed
Failed CI StepsHistory |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What if we put a semantic conventions registry inside an integration?
Kibana could have access to the semantic conventions defined in upstream registries combined with ones defined in integrations.
Integrations that use ECS fields could define these as semconv attributes and metrics in their respective registries.
The example in this PR is as simple as possible, since all of the conventions defined here come from the
importfrom OpenTelemetry semantic conventions.