I guess, first things first. Is there even such a thing (these days) as .jar file that I can include into my project and use the Otel APIs or is that a thing of the past and it is done completely different these days?

I guess, first things first. Is there even such a thing (these days) as .jar file that I can include into my project and use the Otel APIs or is that a thing of the past and it is done completely different these days?

I am working on a distributed system that involves EMQX receiving data and sending it to a Confluent Kafka server. I want to implement automatic context propagation using OpenTelemetry across these services, but I’m unsure how to handle this since I’m using Confluent Kafka, not the Kafka SDK directly.

At work, they asked me to use https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver inside our opentelemtry collector agent. The problem is they are asking for a feature to skip log files if their size increased unreasonably.

I am just getting stated with OpenTelemetry and I am trying to process the raw data for analysis.

I’m trying to understand what the requirements is for scope in OpenTelemetry I read the example in the OpenTelemetry but failed understand the actual propose of this.

I’m trying to figure out how to properly configure my receivers for journald. When I, naively, run otelcol --config=my-config.yaml I’m getting

My application processes messages from rabbit queue. Lots of the messages are inappropriate for processing (not ideal, but for a valid reason), so the application is just rejecting them upon reading without re-queuing them.
As the messaging library (aio_pika) is otel instrumented, it generates loads of unnecessary spans that are exported. What is the best way to exclude these spans from being exported?