open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
581 Commits 2 Branches 18 Tags 34 MiB
Commit Graph

581 Commits

Author SHA1 Message Date
Joao Grassi a0a6f5c0e9
Fix IBM J9 API ref broken links (#92) 2023-06-07 18:52:49 +02:00
Alexey Basinov d6d29521bc
Add Google Bare Metal Solution as a cloud platform (#64) 
Co-authored-by: Joao Grassi <joao@joaograssi.com>
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
 2023-06-05 16:50:28 -04:00
Trask Stalnaker 9dc02df2e0
HTTP duration metrics should match HTTP span duration (#69) 2023-06-02 10:38:06 -07:00
Mike Dame 4f211389fd
Add GCP Compute Engine resource attributes for host/instance (#15) 
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
 2023-06-01 10:46:31 -04:00
Trask Stalnaker 62513fbc50
Clarify `process.runtime.jvm.threads.count` refers to platform threads (#54) 2023-05-31 16:12:03 +02:00
jdoherty eacb63da11
Updated Documentation For Change in Behaviour of Reading X-Ray Tracing Info From Lambda (#27) 
Co-authored-by: Tyler Benson <tylerbenson@gmail.com>
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
 2023-05-25 08:18:31 -04:00
Josh Suereth 350b501c27
Remove status documents and link to published specification. (#47) 2023-05-23 18:02:09 +02:00
Josh Suereth 4c5194ae78
Update all links to the specification to point at the 1.21.0 release (#45) 2023-05-23 11:50:37 -04:00
Tigran Najaryan 1f4dc6890e
Add tigrannajaryan as schema and logs codeowner (#28) 2023-05-19 16:15:06 -07:00
Carlos Alberto Cortez 0887921aed
Update CHANGELOG with missing entry. (#36) 2023-05-17 11:43:45 +02:00
Gregor Zeitlinger 3a0a2d9031
describe JVM CPU metrics (#13) 
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
 2023-05-16 12:30:28 -04:00
Josh Suereth b5bcbccc17
Add a tool that allows us to quickly update specification URLs to a s… (#9) 
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
Co-authored-by: Johannes Tax <johannes@johannes.tax>
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
 2023-05-16 12:25:46 -04:00
Armin Ruech 3bb601c243
Update team names following #25 (#29) 2023-05-15 09:16:04 -07:00
Josh Suereth c0731b9ae9
Remove tech committee from maintainers. Semconv will have its own set. (#25) 2023-05-15 11:15:34 -04:00
Mike Dame 5b25f380cb
Add CHANGELOG.md (#18) 2023-05-15 10:11:50 -04:00
Liudmila Molkova c5f7a17b34
Editorial: minor fixes for HTTP spec (#16) 2023-05-12 12:21:55 -07:00
Josh Suereth 7c606855bf
Add CODEOWNERS and automation around ownership (#7) 
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
 2023-05-11 13:14:38 -04:00
Josh Suereth 9976b2abba
Add pull request checks back for links/markdown. (#5) 2023-05-11 12:57:26 -04:00
Josh Suereth ba20753993
Remove no-changes allowed header from new repository. (#6) 2023-05-11 11:46:04 -04:00
Armin Ruech 0ff54340ef
Fix contributor names and teams (#8) 
Fixed the team names, some links, as well as @MovieStoreGuy's and my
name 🙂
 2023-05-11 11:44:08 -04:00
Josh Suereth 4c14e25241 Add readme/contributing. 2023-05-11 08:24:31 -04:00
Josh Suereth 554a97dde2 Put hiatus on semantic conventions until they are in the new repository. (#3489) 
As per OTEP:
https://github.com/open-telemetry/oteps/blob/main/text/0227-separate-semantic-conventions.md
 2023-05-11 05:59:41 -06:00
Tyler Benson f6bee62bfd Add requirement to use X-Ray propagation for aws-sdk client calls (#3212) 2023-05-08 21:22:58 -07:00
Mike Dame 56c77bacd6 Add detail for GCP Cloud Run Job execution (#3378) 2023-05-08 21:18:54 -07:00
Liudmila Molkova 614dbefc77 BREAKING: Introduce common `url.*` attributes, and improve use of namespacing under `http.*` (#3355) 2023-05-08 19:55:53 -07:00
Trask Stalnaker 9e3e528ccc BREAKING: Rename remaining network attributes from `net.*` to `network.*` and align definitions with ECS (#3426) 2023-05-08 17:46:55 -07:00
Liudmila Molkova 5b8861e8c5 BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) (#3402) 2023-05-08 16:19:51 -07:00
Robert Toyonaga 239caf82ac Add JVM runtime metric source API notes (#3463) 
Fixes #3418

## Changes

Add notes on where the JVM runtime metrics come from.

---------

Co-authored-by: Mateusz Rzeszutek <mrzeszutek@splunk.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: jack-berg <34418638+jack-berg@users.noreply.github.com>
 2023-05-08 14:26:28 -05:00
Trask Stalnaker 3f8cd16996 Transition plan for HTTP breaking changes where both old and new attributes can be sent for a while (#3443) 2023-05-08 12:00:16 -07:00
jack-berg 8f0a652071 JVM gc duration unit and bucket boundaries (#3458) 2023-05-03 09:47:34 -07:00
Trask Stalnaker ed7b11c28d Add explicit status to all sub-sections in "Mixed" document (#3460) 2023-05-01 08:48:20 -07:00
Cijo Thomas a2e3100848 Add Rust to the telemetry.sdk.language resource convention (#3448) 2023-04-26 12:42:23 -07:00
jack-berg 31485588b2 Move configuration documents to configuration folder (#3434) 2023-04-25 14:51:27 -07:00
Robert Pająk 2ef975b7b2 Refactor Telemetry SDK resource detector description (#3392) 2023-04-25 08:00:38 -06:00
Johannes Tax 15f3e529f1 BREAKING: Remove `messaging.consumer.id`, make `messaging.client_id` generic (#3336) 
Fixes #2015

## Changes

Based on discussions in the messaging workgroup and in issue #2015, this
PR proposes to remove `messaging.consumer.id`, and to replace both
`messaging.kafka.client_id` and `messaging.rocketmq.client_id` with a
generic `messaging.client_id`.

`messaging.consumer.id` is defined to always be set to the `client_id`
of the used messaging system, except for Kafka, where it was defined to
be a combination of `messaging.kafka.client_id` and
`messaging.kafka.consumer.group`, or just the latter if
`messaging.kafka.client_id` is not available. With this definition, the
semantics of `consumer.id` are different between messaging systems, and
even different for different Kafka scenarios.

The proposed `messaging.client_id` has consistent semantics ("an unique
client id, when it is available"), and can be used instead of
`messaging.consumer.id` in almost all cases.

In addition to have consistent semantics, this also simplifies the
semantic conventions, as instead of

`messaging.consumer.id`
`messaging.kafka.client_id`
`messaging.rocketmq.client_id`

there is now just:

`messaging.client_id`.
 2023-04-24 17:13:21 -06:00
Trask Stalnaker 92a5b9ef64 Fix JVM buffer pool attribute description (#3423) 
Follow-up to #3413

---------

Co-authored-by: jack-berg <34418638+jack-berg@users.noreply.github.com>
 2023-04-21 09:59:59 -05:00
Trask Stalnaker e4613f98af Converts JVM metrics to yaml (#3413) 
Converts JVM metrics to yaml
 2023-04-20 13:56:48 -05:00
Matthew Wear aa873f0a9b add k8s.cluster.uid resource attribute semconv (#3267) 
Fixes #3266

## Changes

Kubernetes doesn't have a formal way to identify a cluster, but a
pseudo-id can be derived by taking the `uid` of the `kube-system`
namespace. This PR adds a convention for `k8s.cluster.uid` to be set to
the `kube-system` namespace uid.
 2023-04-18 15:21:28 -06:00
Trask Stalnaker bce030702e Adds a note about not splitting UpDownCounter timeseries (#3367) 2023-04-18 09:14:04 -07:00
Trask Stalnaker bb42c33451 Change http.server.duration and http.client.duration units to seconds (#3390) 2023-04-14 20:46:53 -07:00
jack-berg 3250d03e49 Specify seconds unit for measuring durations (#3388) 2023-04-14 10:34:54 -07:00
Trask Stalnaker 7a74f7ae79 Clarification about when to use UCUM c/s variant (#3393) 2023-04-14 09:32:04 -07:00
Trask Stalnaker b94251d236 Mark "Instrumentation Units" and "Instrumentation Types" sections of the general metric semantic conventions as stable (#3294) 2023-04-14 09:18:01 -07:00
Mateusz Rzeszutek 711413a4d7 HTTP client span clarification (#3290) 
Related to
https://github.com/open-telemetry/opentelemetry-specification/issues/3155
and
https://github.com/open-telemetry/opentelemetry-specification/pull/3234

## Changes

This PR contains the less controversial parts of
https://github.com/open-telemetry/opentelemetry-specification/pull/3234;
it describes how the `http.resend_count` attribute should be used, and
proposes two ways of instrumenting HTTP clients.
 2023-04-14 09:16:33 -06:00
Tyler Yahn cf52340b6a Add recommendation to use non-prefixed units for metric instruments (#3312) 2023-04-12 15:56:32 -07:00
Liudmila Molkova 6544326ec3 Editorial: add attribute_group type to log.record (#3374) 2023-04-12 11:14:21 -07:00
Bertrand Martin 6080d1a569 Issues #3132, #3133: Semconv for hardware metrics, network metrics and attributes (#3344) 
Fixes #3132, #3133

## Changes

In semantic conventions for hardware metrics:

* Updated network adapter description
* Changed `type` to `hw.error.type` for the `hw.errors` metric
 2023-04-11 17:18:48 -06:00
Sebastien Rosset 26b305941d Update the description of the `host.image` attribute (#3194) 2023-04-11 18:29:16 +02:00
Christian Neumüller 07721f339c Add back refs to cloud.resource_id lost in FaaS renaming. (#3329) 
These places were removed when #3188 in its original form removed
faas.id without replacement and weren't added back after changing it to
introduce cloud.resource_id instead.

Editorial change, no CHANGELOG or issue.
 2023-04-11 07:13:14 -06:00
Alan West df32f2ef4c Clarify parameters for emtting a log record (#3354) 
Supersedes #3350

Clarifies the parameters for emitting a log record.

Context was particularly confusing. Context is not a property of the
`LogRecord` data model. Cleans up section of bridge API spec that seems
to suggest that Context is a field of `LogRecord`. Also, clarifies that
Context can be associated with an emitted LogRecord. We have similar
language in the trace API that leaves room for languages to achieve this
in an idiomatic way. See


d25734a47e/specification/trace/api.md?plain=1#L365-L370

---------

Co-authored-by: Reiley Yang <reyang@microsoft.com>
 2023-04-08 10:42:13 -05:00