semantic-conventions
semantic-conventions copied to clipboard
Defines standards for generating consistent, accessible telemetry across a variety of domains
As part of https://github.com/open-telemetry/semantic-conventions/pull/312, @tigrannajaryan suggested that we should discuss how a Collector can refine an existing service.instance.id. This issue is to collect ideas related to that.
We don't have a group that would: - own/review/approve general logs and events definitions - https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/logs.md - https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/events.md - triage issues in [`area:event`](https://github.com/open-telemetry/semantic-conventions/labels/area%3Aevent) and [`area:log`](https://github.com/open-telemetry/semantic-conventions/labels/area%3Alog)
### Area(s) area:event ### Is your change request related to a problem? Please describe. I want easily visualise my events based on success/failure ### Describe the solution you'd like I...
### Area(s) area:os ### Is your change request related to a problem? Please describe. I want to easily see all my logs from linux machines, just like i can with...
### Area(s) area:os ### Is your change request related to a problem? Please describe. I want to ensure my OS is accurately reported ### Describe the solution you'd like The...
Attribute names can be any unicode sequence https://github.com/open-telemetry/semantic-conventions/blob/dd277f62f66f3342be33aec2c432f6bd959b379b/docs/general/attribute-naming.md?plain=1#L24 It makes sense for user apps using OTel API and OTLP, but is not accepted by our ([build-tools](https://github.com/open-telemetry/build-tools/blob/14261ddd0b14fecb94e9fca3e0690008b83de836/semantic-conventions/src/opentelemetry/semconv/model/utils.py#L20-L23)) tooling ```python ID_RE =...
There could be `cloud.resoure.name` and possibly other properties of a cloud resource. Based on the discussion in#1118, specifically https://github.com/open-telemetry/semantic-conventions/issues/1118#issuecomment-2159136053, we should use `.` instead of `_` where it makes sense....
> currently both of these namespaces are used in this PR: > > * `linux.*` > * and `system.linux.*` > > should we rename `system.linux.*` to `linux.*`? > > that...
# Overview During the pull request feedback, there was a [mention of a need for having consistency in the `url.full`](https://github.com/open-telemetry/semantic-conventions/pull/1075#discussion_r1676436870) so that end users can consistently query across telemetry. We...