9976b2abba
Add pull request checks back for links/markdown. ( #5 )
2023-05-11 12:57:26 -04:00
ba20753993
Remove no-changes allowed header from new repository. ( #6 )
2023-05-11 11:46:04 -04:00
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
56c77bacd6
Add detail for GCP Cloud Run Job execution ( #3378 )
2023-05-08 21:18:54 -07:00
a2e3100848
Add Rust to the telemetry.sdk.language resource convention ( #3448 )
2023-04-26 12:42:23 -07:00
31485588b2
Move configuration documents to configuration folder ( #3434 )
2023-04-25 14:51:27 -07:00
2ef975b7b2
Refactor Telemetry SDK resource detector description ( #3392 )
2023-04-25 08:00:38 -06:00
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
26b305941d
Update the description of the `host.image` attribute ( #3194 )
2023-04-11 18:29:16 +02:00
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
dcd39bf86e
Mark `service` and `telemetry.sdk` resource attributes as stable. ( #3202 )
...
## Changes
This PR marks the set of resource semantic conventions, which a relied
upon in stable API / SDK specification, as stable themselves.
- Add a caveat that changing `service.*` and `telemetry.*` names need
MORE than just schema file changes.
- Mark core Resource attribute semconv document as MIXED stability
- Update key sections for Resource attribute semconv as stable
- Mark `telemetry.sdk` and `service` attribute groups as stable.
- Move `telemetry.auto` and `service.*` "contentious" attributes into
`{section}_experimental.yaml` file. This retains the reserved name, but
does not mark the convention as stable, allowing us to ensure stable
portions of our specification refer to stable semconv.
- Update examples for `service.instance.id` to include an example of the
preferred style instance id before the fallback.
Related issues #3177
## Usage in the Specification
One reason we should mark these attributes as stable is because they are
referenced from numerous stable portions of our specification, and they
are also leveraged from newly stabilizing portions of our specification.
- [Resource
SDK](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md#sdk-provided-resource-attributes )
- stable
- [Environment
Variables](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md#general-sdk-configuration )
- stable
- [Jaeger
Exporter](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk_exporters/jaeger.md#resource )
- stable
- [Zipkin
Exporter](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk_exporters/zipkin.md#service-name )
- Stable
- [Log
DataModel](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#rfc5424-syslog )
- Stable
- [Prometheus
compatibility](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#resource-attributes )
- still experimental
- [Performance Benchmark
Guidelines](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/performance-benchmark.md )
## A note on ECS compatibility
Here's [ECS service
definition](https://www.elastic.co/guide/en/ecs/current/ecs-service.html ).
They include more attributes than we do. The only possible conflict
between us is `service.instance.id` vs. `service.node.name`. In this
case, our `service.instance.id` has a fallback of generating UUID which
is inconsistent w/ `service.node.name` which requires a user-generated
name if another name cannot be provided.
There's an opportunity for us to unify here. However, I don't think
there's appetite in OTEL to require user-specified names in lieu of some
algorithm or generative specification.
2023-04-03 19:40:12 -07:00
6d7b233c80
Rename http.user_agent to user_agent.original ( #3190 )
...
Fixes #3180
## Changes
Renames `http.user_agent` to `user_agent.original`.
2023-03-02 14:47:29 -06:00
47cabcf799
Rename Optional attribute requirement level to Opt-In ( #3228 )
2023-03-01 15:13:24 -08:00
f839f1ed9a
clarify how to collect host.id for non-containerized systems ( #3173 )
2023-02-28 18:17:04 +01:00
2447fb063f
Expand scope of `faas.id` to `cloud.resource_id` ( #3188 )
...
## Changes
As per the discussion on #3188 , we determined it is better to move
rather than remove as this attribute is still important for some systems
despite it containing duplicated information.
2023-02-27 12:13:13 -06:00
12481fef89
add semantic conventions for heroku ( #3075 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-02-27 10:23:29 +01:00
0d0b9d0a7d
Rename `faas.execution` to `faas.invocation_id` and change units for `faas.max_memory` ( #3209 )
2023-02-20 09:29:24 -06:00
1971550982
[editorial] Fix Tencent Cloud link ( #3231 )
2023-02-20 10:29:04 +01:00
e35ad2b9d5
[semantic_conventions/resource] fix google platform openshift naming ( #3095 )
2023-01-23 14:56:48 -08:00
656644592a
[resource] add openshift platform to all supported cloud providers ( #2985 )
2022-12-06 16:52:30 +01:00
6f0cadac7e
List the machine-id as potential source for a unique host.id ( #2978 )
2022-11-29 10:06:04 -08:00
b901d9dd76
add ibm cloud as a cloud provider ( #2965 )
2022-11-21 10:31:32 -08:00
c359bd372c
Add mobile and language semconv for browser resource ( #2761 )
2022-09-20 21:19:02 +02:00
fca9616e41
add process.parent_pid attribute ( #2691 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2022-07-28 16:54:58 +02:00
3f7b7d02f9
Adopt attribute requirement levels in semantic conventions ( #2594 )
2022-06-14 08:02:55 -07:00
6a613c54e4
Add Resource browser attributes ( #2353 )
2022-05-19 10:57:41 -07:00
7d2a40e537
Azure FaaS conventions. ( #2502 )
2022-05-13 12:01:20 -07:00
53ba5dd524
Map SunOS to `solaris` for `os.type` resource attribute ( #2509 )
2022-04-27 14:12:22 -07:00
741ac62a15
Bump semantic conventions tool to v0.11.0 and refine enum wording ( #2399 )
2022-03-04 17:51:37 +01:00
2b026d81db
Define JavaScript runtimes semantic conventions ( #2290 )
2022-03-02 16:18:40 +01:00
4f6af3ae6f
Change golang namespace to 'go', rather than 'gc' ( #2262 )
...
* Change golang namespace to 'go', rather than 'gc'
* Specify common process.runtime.* attributes for Go
* Add link to runtime.Compiler
* Remove static descriptions
* Add table of descriptions for golang runtime names
* Add context to go examples
Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com>
2022-01-27 07:21:21 +00:00
3b50032ecc
Add `device.manufacturer` to semantic conventions for resources ( #2100 )
...
* Update device.md
Proposed manufacturer field
* Update device.md
* Generate tables
* PR comments
* Remove trailing whitespace
* Update CHANGELOG.md
Make linter happy?
* Fix merge
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
2021-12-16 00:22:56 +00:00
fdd5c96846
Clarify difference between `container.name` and `k8s.container.name` ( #1980 )
...
Add more details to container name attributes to clarify the difference.
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
2021-11-04 18:45:20 +00:00
14973d30e6
Add swift to the list of `telemetry.sdk.language` ( #2097 )
2021-11-04 18:38:41 +00:00
de1b890989
Add IBM z/Architecture ( #2055 )
2021-10-28 14:33:18 +02:00
d9fbb6f32c
Add Makefile target to auto-generate TOC via markdown-toc ( #2020 )
2021-10-15 15:04:22 +00:00
540878944d
Add AWS App Runner as a cloud platform ( #2004 )
2021-10-15 15:59:50 +02:00
3e51df22d7
[semantic conventions] add tencent cloud as a cloud provider ( #2006 )
...
* feat: add tencent cloud as a cloud provider
* chore: tweaks
* chore: tweaks
* chore: lint
* chore: changelog
* chore: tweaks
* chore: tweaks
Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com>
2021-10-12 19:02:27 +00:00
d2279afe9e
Add `k8s.container.restart_count` Resource attribute ( #1945 )
...
This change adds a Resource attribute to represent number of container restarts in kubernetes. This is can be used in k8s logs collection to identify a particular container instance, where the number of container restarts is a part of a log file path.
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
2021-10-06 12:10:27 +00:00
227b4ff1b1
[semantic conventions] add alibaba cloud as a cloud provider ( #1831 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
2021-08-03 11:22:31 +00:00
25f029b2e2
Rework FaaS semantic conventions. ( #1781 )
2021-07-06 14:34:09 +02:00
ecec5145dc
Remove examples from enums. ( #1779 )
2021-06-29 12:54:59 -07:00
56e0491893
Add `OTEL_SERVICE_NAME` environment variable ( #1677 )
...
* Add OTEL_SERVICE_NAME environment variable
Closes #709
2021-05-24 15:54:33 +02:00
83a291c491
Add Device (Mobile) and OS Version Resource Semantic Attributes ( #1596 )
...
* Add Device (Mobile) and OS Version Resource Semantic Attributes
* Added OS Name (iOS) and OS Version (14.4) to `os`.
* Added Device Identifier and Model Identifier to a newly created `device` group.
2021-05-20 14:21:47 +02:00
b2c25ee059
fix typo ( #1691 )
...
Should be instrumentation, not insrumentation
2021-05-12 20:55:30 +02:00
bc85b047c2
Have consistent formatting for semantic convention enums ( #1598 )
...
* Have consistent formatting for semantic convention enums
Currently, semantic convention enum values are not consistent.
For example, os.type values are all capitals whereas
cloud.infrastructure_service values are underscored lowercase.
This change improves the inconsistencies.
We also expect language implementations to autogenerate code
from enum values. Each language has their own conventions for
constant variable identifiers and we expect the consistent
formatting is going to help the language implementors.
Fixes #1519 .
2021-04-15 17:43:00 +02:00
4aa113a9f1
Adding webengine definition under resources semantic conventions ( #1293 )
2021-04-01 16:29:36 +02:00
bc787fd36a
Add aws.ecs.task.revision semantic convention ( #1581 )
2021-03-30 16:53:24 +02:00
435182a274
Avoid using "infrastructure" terminology for all cloud ( #1530 )
...
* Avoid using "infrastructure" terminology for all cloud
Infrastructure in cloud has a specific connotation for concepts
explained in Infrastructure-as-a-Service (IaaS). Avoid this
termilogy because it's exclusive of some other services/platforms
that is represented by the "cloud" namespace.
Renaming "infrastructure_service" to "service" also due to the new
key length limits we are considering and infrastructure_service is
a lengthy choice.
2021-03-22 23:56:07 +01:00
561ad88d7f
Update semantic conventions to distinguish int from double ( #1550 )
2021-03-18 17:06:10 +01:00
Josh Suereth