-
### Component(s)
_No response_
### Describe the issue you're reporting
I used https://github.com/Bhoopesh123/OpenTelemetry for setting up Open telemetry on my EKS. Only prometheus metrics are faili…
-
Hi,
I'm using opentelemtry-collector via deployment mode in my kubernetes cluster.
I'm trying to figure out what is the least amount of resource limits I can set to this opentelemetry-collector so…
-
As per @dmitryax's comment, there is insufficient unit test coverage of the telemetry emitted by the collector.
> I'm worried that the emitted internal metrics are not covered by tests. It'll be gr…
-
### Proposal
While trying to play with opentelemetry by running prometheus with the experimental `--enable-feature=otlp-write-receiver` cli argument and the following [opentelemetry-collector-contrib…
-
Currently, the available log driver implementations in container-management are `json-file` and `none`.
For the integration of OpenTelemetry, it would be great to have a log driver implementation s…
-
### Component(s)
connector/spanmetrics, processor/filter
### Describe the issue you're reporting
background:
PromQL: `sum(duration_count{span_name="GET"}) by (span_name)`
Sample: `{span_name="GET…
-
**Describe the bug**
When config `service::telemetry::metrics::readers` contains a prometheus exporter, the collector incorrectly logs a warn message to the console that `address` field is deprecated…
-
**Is your feature request related to a problem? Please describe.**
We found there is no experience like override-configuration-with-environment-variables https://grafana.com/docs/grafana/latest/setup…
-
It would be awesome if I could (...) choose which metadata I want to see.
Eg. for logs sometimes I might be interested only in logs, sometimes in logs and some metadata and sometimes in metadata only…
-
Once this is setup, there is an OTLP endpoint for collecting logs/metrics. That said, there isn't really an end-to-end setup for how to configure this with Alloy. Would it be possible for someone to w…