Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream components for 'Elastic Beats' seem wrong. #165

Open
sa-mustafa opened this issue Jan 30, 2022 · 1 comment
Open

Upstream components for 'Elastic Beats' seem wrong. #165

sa-mustafa opened this issue Jan 30, 2022 · 1 comment

Comments

@sa-mustafa
Copy link

The landscape shows that 'OpenTelemetryCollector' or 'OpenCensusCollector' can connect to 'Elastic Beats'. However, I did not find any documentation on Elastic.co or anywhere else whatsoever. What I found was that Elastic Beats can take metrics/log data and ship them to Elastic Search or Logstash. Community beats do not support OpenTelemetry or OpenCensus collector either. I'd be happy if they do support. Please show me if it is possible.

@tobiangerstein
Copy link
Contributor

tobiangerstein commented Feb 2, 2022

Hi @sa-mustafa, thank you very much for your question and your interest in the openapm.io landscape! Both opentelemetry-collector as well as the opencensus-collector are able to expose metrics with the Prometheus Exposition Format. Elastic Beats are able to collect metrics, which are in that format.

image

In case you want to ship data to an elasticsearch cluster, you might have a look at the existing exporters of the opentelemetry-collector.

Please note, that I would not recommend to use the opencensus collector, as this project is going to be discontinued

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants