-
### Describe the bug
I setup a project to export metrics to otel-collector via java agent but only certain metrics are being sent.
Not exporting:
```
process.*, //Including CPU
system.*, …
-
**What are you trying to achieve?**
I want to add a metric to the semantic conventions that will describe the system uptime. How about `system.uptime`?
**Additional context.**
This is reporte…
-
## Context
Currently, in the `model/**` directory we mix up two things:
- Defining an attribute (with the name, type, description of its semantics, examples)
- Usage of an attribute in a concrete…
-
### Component(s)
extension/oidcauth
### What happened?
## Description
Hi. I want to trace my golang application's metrics with Opentelemetry and Clickhouse. To achieve this, I use the opente…
-
After running JQ `semconv_grouped_metrics`, I still need to sort metrics by metric_name with something like `ctx.metrics | sort(attribute="metric_name")`.
-
Some of the JVM metrics are now stable and are [part of the semantic conventions](https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/).
For example, the `jvm.thread.count` metric ([sem…
-
Proposing a new feature, where user can get the request parameters, i.e. headers, body etc. in resource attributes.
This can be controlled via a feature toggle as @zeitlinger suggested to me on slack…
-
### Area(s)
area:messaging
### What happened?
Last week in https://github.com/open-telemetry/semantic-conventions/pull/948 `messaging.client_id` was renamed to `messaging.client.id`. In the JS code…
-
### What do you want to change?
I propose a mechanism that allows users of the generated code to instrument the Querier.
Use-cases could be, but are not limited to:
* Start Spans for OpenTeleme…
kyuff updated
1 month ago
-
This issue describes a concrete proposal on [how to realise attributes reuse](https://github.com/open-telemetry/semantic-conventions/issues/339) through yaml syntax and tooling.
## Related issues /…