-
**Is your feature request related to a problem? Please describe.**
Users define `component.ID`'s in their collector configurations using the format `type[/name]` where `type` is for example `otlp` …
-
# Feature Request
Add a new Go service (or migrate a current one) that can be auto-instrumented with Go: https://github.com/open-telemetry/opentelemetry-go-instrumentation.
The Dockerfiles can reu…
-
Sense Collector - Collector Info
Void of all data
Device Detection Status: and In Progress Devices no populated on the Sense Collector - Monitor & Detection
all other data on this page is presen…
-
### Is your feature request related to a problem? Please describe.
We currently do not support well OpenShift.
### Describe the solution you'd like
We want to support OpenShift as a first class sup…
-
### Component(s)
receiver/prometheus
### Is your feature request related to a problem? Please describe.
I don't know if there was something already exists.
OTel has kubeletstatsreceiver and k8sc…
-
Dear Amazon Corretto Support Team,
I hope this message finds you well. We recently migrated our product from Java 8 to Amazon Corretto Java 17, and after the migration, we noticed a significant inc…
-
### The purpose and use-cases of the new component
The new component, Prometheus remote write receive, is designed to enable OpenTelemetry collectors to receive metrics data from Prometheus instanc…
-
### Description
We've configured Keycloak to work with OpenTelemetry (OTEL) following the official documentation (https://www.keycloak.org/server/tracing). While we're able to see traces in Jaeger, w…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
We need to update the README and the toml configurations to ensure that we are consistent with the Automate URL configuration. I think we need to support both with and without the `/data-collector/v0/…