[receiver/faro] Updates faroreceiver http server to respond to collect calls with http.StatusAccepted (status code 202) as per the faro openAPI schema #45648
+31
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lect calls with http.StatusAccepted (status code 202) as per the faro openAPI schema
Contributor
|
Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib. Important reminders:
A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better! |
…e http.StatusAccepted (202) status code
rlankfo
approved these changes
Jan 26, 2026
vanugrah
changed the title
vanugrah
changed the title
vanugrah
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Hey folks - this is a small PR to update the faroreceiver http response code to conform to the official Faro OpenAPI Schema. In addition we can also see that this is what is followed by Faro collector in Grafana Alloy.
Link to tracking issue
Given that this is such a small PR I have not created a issue for it yet. If this is a required step - I'm happy to create one.
Testing
Ran the fork in a docker compose environment to validate the response codes are now returning status 202 to conform to the OpenAPI spec.
Documentation
No docs added.