Closed M0NsTeRRR closed 1 month ago
Thanks for this very detailed report @M0NsTeRRR ! I'll add the gzip compat to the http endpoints. Out of curiosity, why are you not using the GRPC exporter? That one should work fine even with compression enabled.
Thanks for this very detailed report @M0NsTeRRR ! I'll add the gzip compat to the http endpoints. Out of curiosity, why are you not using the GRPC exporter? That one should work fine even with compression enabled.
You're welcome. I will in the future as I'm working on deploying API Gateway in my Kubernetes cluster. Since it's not available for now, I prefer to use the HTTP endpoint for simplicity.
Describe the bug OTLP HTTP logs endpoint with compression (gzip/zstd) gives an HTTP error 400. Unfortunately, Alloy doesn't display error messages like Quickwit does. However, I encountered the same behavior with a Python script, and I was able to see the error message. If I disable compression it works.
alloy logs
python logs
Steps to reproduce (if applicable) Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Configuration:
pip install opentelemetry-exporter-otlp-proto-http
and launch the below script withREQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt OTEL_EXPORTER_OTLP_LOGS_COMPRESSION=gzip python script.py
.OTEL_EXPORTER_OTLP_LOGS_COMPRESSION
can be set tonone
Python script
compression = "none"
works.Alloy config
quickwit --version
: Quickwit 0.8.1 (x86_64-unknown-linux-gnu 2024-03-29T14:09:41Z e6c5396)Quickwit config