semantic-conventions

semantic-conventions copied to clipboard

Capture request and response bodies

14

**What are you trying to achieve?** I want to capture request and response bodies. The content can be used for business transaction monitoring and security. To move this forward we...

pavolloffay

Clarify relationship between messaging, faas, and RPC

20

I want to clarify the relationship between messaging, RPC, and FaaS which is confusing to me right now. Let me give an example, based on my understanding of the current...

anuraaga

Merge *.cpu.state attributes to a common cpu.state attribute

2

Fixes https://github.com/open-telemetry/semantic-conventions/issues/840 ## Changes This PR introduces a common `cpu.state` attribute which is a converged attribute from the `system.cpu.state`, `process.cpu.state` and `container.cpu.state`. ## Merge requirement checklist * [x] [CONTRIBUTING.md](https://github.com/open-telemetry/semantic-conventions/blob/main/CONTRIBUTING.md) guidelines...

ChrsMark

Introduce common `messaging.consumer.group.name` and `messaging.destination.subscription.name` instead of per-system ones

2

## Changes Addresses consumer group and subscription name part of #797 ## Merge requirement checklist * [x] [CONTRIBUTING.md](https://github.com/open-telemetry/semantic-conventions/blob/main/CONTRIBUTING.md) guidelines followed. * [x] Change log entry added, according to the guidelines...

lmolkova

Add initial experimental .NET CLR runtime metrics

37

Fixes #956 ## Changes Adds proposed experimental .NET CLR runtime metrics to the semantic conventions. Based on [discussions with the .NET runtime team](https://github.com/dotnet/runtime/issues/85372), the implementation plan will be to port...

stevejgordon

This is a prototype of using Weaver to enforce semantic convention policies via the experimental Open-Policy-Agent support. This defines three policies: - `nonregistry_with_id_attr`: We only allow new attribute definitions inside...

jsuereth

DB Span name format with alternating attributes

1

Currently the [spec for db span names](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md#name) defines the span name in the format of `{db.operation.name} {target}` with a specific list in prioritized order. That works very well when within...

gregkalapos

DB sanitization uniform format

8

**What are you trying to achieve?** According to the [db spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md#call-level-attributes), the `db.statement` value can be sanitized, but it is not defined how to do so. Currently, the sanitization is...

avzis

Follow up from https://github.com/open-telemetry/semantic-conventions/pull/974#discussion_r1584002801. ## Changes - Align Elasticsearch span names with the format defined in the general db spec. MongoDB is comparable and it already follows this format. The...

gregkalapos

[cloud provider] Add AWS EC2 instance id semantic convention

19

## Changes Add semantic convention for AWS EC2 instance id. This is similar to #15, and is inspired by #576, to ensure that the EC2 instance id can be correctly...

mx-psi