This repository was archived by the owner on Jan 12, 2026. It is now read-only.
Update README to include nuance from OTEL collector#289
Open
Forcebyte wants to merge 1 commit intosplunk:developfrom
Open
Update README to include nuance from OTEL collector#289Forcebyte wants to merge 1 commit intosplunk:developfrom
Forcebyte wants to merge 1 commit intosplunk:developfrom
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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
This adds a small amount of clarity to the Fluentd collector, from what I read:
This wasn't fully captured in the fluent-plugin repo, so adding it here for prosperity
See https://github.com/signalfx/splunk-otel-collector-chart/?tab=readme-ov-file#current-status from where this information is sourced