-
-
* How can we improve collaboration?
* How can we make it easier for implementing SIGs to address their needs?
* How can we help the Spec/SemConv to find SIGs that provide reference implementation?
svrnm updated
2 months ago
-
Hello all (@open-telemetry/php-approvers) 👋🏽
As I've briefly explained during the SIG Meeting, the DevEx SIG is running a survey with other SIGs, to collect feedback from the approvers and maintai…
-
Client instrumentations have a concept of a session that spans many traces and events/logs. Per [semantic conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/ses…
-
We restrict attribute types to primitives and array or primitives and make an exception for `LogRecord`.
https://github.com/open-telemetry/opentelemetry-specification/blob/e9a2b004ccf547871c5208aa9…
-
## Current Status
Current (latest) package of `@opentelemetry/semantic-conventions` uses semconv version v1.7.0, as seen in `scripts/semconv/generate.sh`.
There are breaking changes in semantic …
-
Based on the messaging SIG discussion on 2/15/24, we should target stabilizing Kafka and RabbitMQ semconv along with the messaging semconv stability.
While we can always add span attributes, but ad…
-
There is an ongoing effort to migrate all code generation to [Weaver](https://github.com/open-telemetry/weaver) (see this [issue](https://github.com/open-telemetry/weaver/issues/227) tracking this eff…
-
Imagine I'm instrumenting kafka:
- there could be some events I'd emit - e.g. cluster leader is unreachable - which are documented in the semconv
- there could also be things I just want to let my u…
-
### What version of OpenTelemetry are you using?
"@opentelemetry/api": "^1.9.0"
"@opentelemetry/auto-instrumentations-node": "^0.50.0"
"@opentelemetry/exporter-trace-otlp-http": "^0.53.0"
"@open…