Closed makigurapo closed 1 year ago
This is unexpected. What collector build / version are you running?
This issue was marked stale due to lack of author feedback. It will be closed in 7 days.
Closed as inactive. Feel free to reopen if this issue is still being worked on.
Having the same issue here with 1.22.1 version of the Java agent, trying to use the OTLP GRPC exporter
What version of the collector are you using?
What version of the collector are you using?
Sorry, I don't really know. I'm trying to set things up with a third party provider - Instana. I doubt their version is very old. What are the supported collector versions?
hi @yassenb! can you check with your backend provider if they support OTLP metrics ingestion, and if you are using the correct setup for their OTLP service?
hi @yassenb! can you check with your backend provider if they support OTLP metrics ingestion, and if you are using the correct setup for their OTLP service?
So I managed to get it working but only by running a collector locally with an OTLP GRPC exporter configured. I couldn't find any documentation on it but circumventing the collector and exporting directly should work just the same right? There seems to be some difference between what the collector OTLP GRPC receiver accepts and what the OTLP GRPC exporter sends which makes the open telemetry collector a mandatory component. I understand the benefits of the collector but for now would like to go without it, what is the proper way to do it?
If your vendor accepts OTLP directly they may be doing so without the collector. There may be something wrong (or different than the collector) in their implementation of the OTLP receiver protocol that is causing the problem.
Hi, I'm also having the same issue:
after running the curl command. (ERROR)
and this what happens of microservice:
and this current value of run-microservice file:
and this is the value of collector-config-local.yaml