Open jennydaman opened 5 months ago
Hello,
I had the same issue. I searched through GitHub and saw that OTLP HTTP was implemented in #4335. The endpoint looks like https://demo.quickwit.fr/api/v1/otlp/v1/logs
for logs (replace logs
with traces
for trace endpoint).
https://github.com/quickwit-oss/quickwit/blob/main/quickwit/quickwit-serve/src/rest.rs#L244 https://github.com/quickwit-oss/quickwit/blob/main/quickwit/quickwit-serve/src/otlp_api/rest_handler.rs#L61
It looks like the endpoint is bugged with compression (tested with grafana alloy and a custom script).
This config works
otelcol.exporter.otlphttp "log" {
client {
endpoint = "https://demo.quickwit.fr"
compression = "none"
tls {
insecure = true
insecure_skip_verify = true
}
}
logs_endpoint = "https://demo.quickwit.fr/api/v1/otlp/v1/logs"
}
The compressions issue was resolved in https://github.com/quickwit-oss/quickwit/pull/5260
Hi there,
I am developing a Rust service using the opentelemetry-otlp crate, and I am evaluating Quickwit for tracing.
Project: https://github.com/FNNDSC/oxidicom
Sadly, an important dependency of my library is not async, so I cannot use gRPC (which depends on the tonic crate, which depends on async). In my Cargo.toml I have opentelemetry-otlp installed with these features:
I am able to ship traces to an OpenTelemetry collector just fine. For efficiency, I would like to consider cutting out the middle man and sending my traces directly to Quickwit without using the OpenTelemetry collector.
https://quickwit.io/docs/distributed-tracing/overview <-- here it says:
However, I can't find any documentation about how to ingest HTTP OTEL data.
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://quickwit:7280
and gotOpenTelemetry trace error occurred. HTTP status client error (405 Method Not Allowed) for url (http://quickwit:7280/)