update the datadog exporter to support the orchestrator explorer #44523
+229
−139
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
github-actions
bot
added
pkg/datadog
internal/datadog/e2e
exporter/datadog
github-actions
bot
requested review from
IbraheemA,
ankitpatel96,
dineshg13,
jackgopack4,
jade-guiton-dd,
liustanley and
mackjmr
kangyili
force-pushed
the
kangyi/add-orch-explorer
branch
from
653f257 to
52ef475
Compare
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
Related PR: DataDog/datadog-agent#42786
This PR:
github.com/DataDog/datadog-agent/comp/otelcol/otlp/components/exporter/logsagentexporterto the main branch commit DataDog/datadog-agent@cc7b409e194e that includes support for Orchestrator Explorer in the logs component.logsagentexporter.Configto include the orchestrator settings.cluster_namefield from the exposed orchestrator explorer configuration, as cluster name should be handled via thek8s.cluster.namelog attribute.