Add distsearch.conf to Stream Search Command examples - #431
Merged
bparmar-splunk merged 2 commits intoFeb 2, 2022
Merged
bparmar-splunk merged 2 commits into
bparmar-splunk merged 2 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Merged
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
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.
The provided examples of Splunk Streaming Search Commands do not include a distsearch.conf, and as a result the streaming search command fail in a distributed search unless the app is also installed locally on all distributed search peers (indexers).
As per the Splunk Developer documentation at https://dev.splunk.com/enterprise/docs/devtools/customsearchcommands/packageanddeploycustom/#Deploy-a-streaming-command-on-an-indexer a distsearch.conf should be included so the lib directory is distributed.
I have also raised this as an issue #418
I have included both the classic (<=8.2) and new language-bias friendly (>=8.3) syntax for this configuration.