Document behavior of absent Splunk sourcetype in Custom Destinations - #3426
Merged
api-clients-generation-pipeline[bot] merged 1 commit intoApr 17, 2026
Merged
Conversation
api-clients-generation-pipeline
Bot
requested review from
a team
as code owners
April 16, 2026 15:48
api-clients-generation-pipeline
Bot
force-pushed
the
datadog-api-spec/generated/5475
branch
from
April 17, 2026 11:42
c5bd1fc to
fcc06c3
Compare
MintsInc
approved these changes
Apr 17, 2026
api-clients-generation-pipeline
Bot
deleted the
datadog-api-spec/generated/5475
branch
April 17, 2026 12:36
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See DataDog/datadog-api-spec#5475 Test branch datadog-api-spec/test/marjolaine/LOGSF-1545/splunk-sourcetype-in-custom-destinations-edit-doc