OpenTelemetry differents endpoints for logs, metrics and traces #23
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
Signed-off-by: Nicolas Lamirault <[email protected]>
Collaborator
Can you tell us more about your use case here? In general, users can feed in-app telemetry data back into HyperDX unless they want to send the data to different platforms. Typically, consolidating all sources into a single panel makes debugging much easier. |
Collaborator
|
Closing this PR as stale since it's been 6 months and much has changed in the helm chart code base. @nlamirault please feel free to open an issue to discuss an approach and a new PR once we're settled the design. |
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.
With this PR you could use different endpoints for OpenTelemetry data.