OpenTelemetry Collector v0.109.0 Memory Spike & Undefined Exporters Dropping Logs Behind NGINX Ingress
I’m encountering a significant memory usage issue after upgrading our OpenTelemetry Collector from v0.94.0 to v0.109.0. The collector is deployed as a Kubernetes deployment behind an NGINX ingress. Within five minutes of deployment, the pod’s memory usage spikes to 80% of its available memory and remains at that level without decreasing.
I’m trying to write a WebAPI endpoint to collect OTEL telemetry exported by my application
I’m new to OTEL. I may be doing this completely wrong, based on wrong assumptions or misunderstanding of the model.
How to use OpenTelemetry Collector to query multiple databases as a metric
I’m currently using the sqlquery receiver of the OpenTelemetry Collector to query a single database for custom metrics. Now, I need to expand this query to cover multiple data sources. With 20 databases to query, copying and pasting the same query and metric configurations results in about 2000 lines of code, which is unreadable, unmaintainable, and prone to errors.
Does anyone have suggestions or best practices for efficiently managing queries across multiple databases?