-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
otel collector not able to send metrics to elastic apm #36546
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
APM Server vs elasticsearchexporterI see that you are using APM server, which is responsible for receiving otlp and sending to Elasticsearch. You should not use elasticsearchexporter when using APM Server, as it send to Elasticsearch directly, which is also why it "complains that it’s not a valid Elastic server" when you tried to point elasticsearchexporter at APM Server. unsupported data pointsAssuming you want to use APM server, there are data points that APM server does not support now, for example, exponential histogram (see issue elastic/apm-server#7614). Can you use a debugexporter to see if your data contain any exponential histograms? |
/label -needs-triage |
hi @carsonip, Thank you for looking into this issue.
|
update!with the latest otel java instrumentation package i am able to send metrics to my apm end point but few errors still persist package used:- https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v2.10.0 error :- pls do suggest how can i fix it. |
@madhureddy143 are there any more |
According to docs, to emit |
@carsonip, thank you for the help, after the package update only jvm.system.cpu.utilization is missing. will try ur suggestion below
|
i re ran with the flags and i can see the CPU utilization in my Kibana dashboard, thank you for your help. |
Component(s)
exporter/elasticsearch
What happened?
Description
We are attempting to use OpenTelemetry Collector with Elastic APM in a Docker Compose-based setup. The installation includes:
The stack is running without any issues.
Current Setup
We are using a model where the OpenTelemetry Java Auto-Instrumentation agent sends logs, metrics, and traces to the OpenTelemetry Collector.
Troubleshooting Steps Taken
Tried Different Exporter Configurations:
otlp
otlp/apm
otlp/elastic
otlphttp
otlp/httpprobf
otlphttp/elasticsearch
otlp/http
ElasticSearch Exporter:
Tried Transformations:
Verified Version Compatibility:
Request for Help
Could you suggest which exporter configuration we should use to ensure that metrics are exported correctly to Elastic APM? If additional transformations or configurations are required, guidance on that would also be appreciated.
Steps to Reproduce
docker compose file
env file for docker compose
application server otel java configuration file
Expected Result
successfully send metrics to elastic APM, which in turn visualized in Kibana
Actual Result
metrics are not visualized in Kibana
Collector version
v0.114.0
Environment information
Environment
os :- ubuntu
deploymet mode:- docker image - otel/opentelemetry-collector-contrib:v0.114.0
app type - java app deployed in tomcat [ using otel java auto instrumentation jar file ]
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: