-
DB semconv:
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/database-metrics.md
-
### Component(s)
exporter/elasticsearch
### Is your feature request related to a problem? Please describe.
When `mapping.mode: ecs` is used, certain OTel + SemConv fields are [converted](http…
-
### Area(s)
area:process
### Is your change request related to a problem? Please describe.
We require any of the following attributes to be present
https://github.com/open-telemetry/semant…
-
### Component
OpenTelemetry.Instrumentation.StackExchangeRedis
### Package Version
Microsoft.Extensions.Hosting 8.0.0
OpenTelemetry 1.9.0
OpenTelemetry.Api 1.9.0
OpenTelemetry.Exporter.Ope…
-
### What happened?
The logs of the [example]( https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-appender-tracing/examples/basic.rs) do not contain `telemetry.sdk.*` resou…
-
**Describe the bug**
As a first timer, I tried the openai instrumentation, and sent a trace to a local collector (using ollama as the backend). Then I compared the output with [llm semantics defined …
-
HBase has native instrumentation in java - https://github.com/apache/hbase/blob/master/hbase-common/src/main/java/org/apache/hadoop/hbase/trace/HBaseSemanticAttributes.java
But hbase semconv does n…
-
The idea is to create a new folder for each version of semantic conventions release and instrumentation packages or end users can choose which one to use.
The folder structure will look like follo…
-
(split from #79)
See https://github.com/open-telemetry/build-tools/pull/79/files#r996803040 for the previous discussion and proposals.
Two possible options would be:
> 1. A table of metric na…
-
As we discovered in #1031, certain semantic conventions changes (together with default code generator behavior) result in ambiguous constant names generated in the code.
For example, when `foo.bar_…