-
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
Unable to export traces to elastic search engine backend #33294
Comments
This appears to be a problem with the backend? Maybe someone from elastic can help here. Pinging @andrzej-stencel |
It looks like you are trying to send traces to Elasticsearch using the OTLP exporter, but Elasticsearch does not accept OTLP directly, unless you add the APM Server in front of it. Instead, you should use the Elasticsearch exporter to export traces to Elasticsearch. |
Hello @andrzej-stencel , when tried with elasticsearch/trace exporter pod going to crash loopbackoff saying with below error
|
I am using elasticsearch exporter to send traces from opentelemetry collector to elastic search engine backend i am facing below error: 2024-06-10T08:26:26.838Z error [email protected]/elasticsearch_bulk.go:315 bulk indexer flush error {"kind": "exporter", "data_type": "traces", "name": "elasticsearch", "error": "failed to execute the request: the client noticed that the server is not Elasticsearch and we do not support this unknown product"} |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
I am not able to export generated traces from opentlemetry collector to elastic search backend, when i checked logs of collector pod it results with below error:
Logs:
2024-05-29T08:37:01.246Z info exporterhelper/retry_sender.go:118 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "traces", "name": "otlp", "error": "rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: http2: frame too large"", "interval": "5.746427186s"}
2024-05-29T08:37:03.504Z warn zapgrpc/zapgrpc.go:193 [core] [Channel open-telemetry/opentelemetry-helm-charts#1 SubChannel open-telemetry/opentelemetry-helm-charts#2]grpc: addrConn.createTransport failed to connect to {Addr: "X.X.X.X:9200", ServerName: ":9200", }. Err: connection error: desc = "error reading server preface: http2: frame too large" {"grpc_log": true}
Otel exporter configuration:
exporters:
logging:
verbosity: detailed
otlp:
endpoint:
headers:
Content-Type: "application/json"
tls:
insecure: false
ca_file:
cert_file:
key_file: >
min_version: "1.2"
max_version: "1.3"
endpoint will be https://:9200/v1/traces
The text was updated successfully, but these errors were encountered: