We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From the OTel spec:
If the server receives an empty request (a request that does not carry any telemetry data) the server SHOULD respond with success.
Honeycomb responds with 400: Request body should not be empty
400: Request body should not be empty
Additional context Reported by a customer.
❯ curl -i https://api.honeycomb.io/v1/traces -H "Content-Type: application/json" -H "x-honeycomb-team: $HC_KEY" -X POST -d '{}' HTTP/1.1 200 OK Connection: close HTTP/1.1 400 Bad Request Date: Thu, 11 Apr 2024 03:09:42 GMT Content-Type: application/json Content-Length: 46 Connection: keep-alive Access-Control-Allow-Origin: * Vary: Accept-Encoding {"message":"request body should not be empty"}% ❯ curl -i http://localhost:4318/v1/traces -X POST -H "Content-Type: application/json" -d '{}' HTTP/1.1 200 OK Content-Type: application/json Date: Thu, 11 Apr 2024 03:09:51 GMT Content-Length: 21 {"partialSuccess":{}}%
The text was updated successfully, but these errors were encountered:
No branches or pull requests
From the OTel spec:
Honeycomb responds with
400: Request body should not be empty
Additional context
Reported by a customer.
The text was updated successfully, but these errors were encountered: