feat(receiver-mock): update /api/v1 to match the latest otelcol version #513
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
aboguszewski-sumo
approved these changes
May 25, 2023
Contributor
aboguszewski-sumo
left a comment
aboguszewski-sumo
left a comment
There was a problem hiding this comment.
LGTM, could you leave a link with documentation to this API somewhere in this PR?
Contributor
Author
Is there any public documentation? I was reverse-engineering 🙈 |
Signed-off-by: Dominik Rosiek <[email protected]>
sumo-drosiek
force-pushed
the
drosiek-collector-api
branch
from
0f8332c to
786f693
Compare
Contributor
|
Then leave it 😔 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following changes:
atodrop-rate, because of build errors/otCollectors/metadataendpoint/collector/{logs,metrics,traces}endpoint referring torouter::otlpCollectorRegisterResponeserialization keysBearerauthorizationI'm considering the following changes:
CollectorRegisterResponeproperties instead of renaming it during serializationBasicauthorization