CODEWITHSUNDEEP
kubernetesloggingopen-telemetryargo-workflows
Vsevolod Mitskevich
Vsevolod Mitskevich

Reputation: 9

Could open-telemetry collector be used without instrumentation?

We are building application with argo workflows. We are wondering if we could just set up opentelemetry collector inside of our kubernetes cluster, and start using it as stdout exporter into elastic stack. Couldn't find information if OTEL can export logs without instrumentation. Any thoughts?

Upvotes: 0

Views: 930

Answers (2)

john smith
john smith

Reputation: 568

As indicated by the following OpenTelemetry (Otel) website:

https://opentelemetry.io/docs/concepts/data-collection/

the Receiver component of Otel Collector can be either push or pull based. For example, using the following Java agent of Otel Collector:

https://github.com/open-telemetry/opentelemetry-java-instrumentation

a Spring Boot jar can be bootstrapped with such an agent without the need to change any code inside this Spring Boot app and still be able to push the telemetry data onto the Otel Collector. Another example is to use a puller instance of Otel Collector to pull the telemetry data out of a Redis runtime using the following example:

https://signoz.io/blog/redis-opentelemetry/

Upvotes: 0

Michael Hausenblas
Michael Hausenblas

Reputation: 14001

The short answer is: yes. For logs you don't need instrumentation, in principle.

However, logs are still in development (so, you'd need to track upstream and deal with the fact that you're operating against a moving target. There are a number of components upstream you can use, for example, you can use the Filelog Receiver and the Elasticsearch Exporter in a pipeline. I recently did a POC and demo (just ignore the custom collector part and use upstream) that you could use as a starting point.

Upvotes: 2

Related Questions