Repository navigation
Keep alert action logs in _internal when CIM is installed (3.1.1) - #71
Merged
Merged
Conversation
…pe and release 3.1.1
ghuang-splunk
approved these changes
Oct 13, 2026
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.
Summary
slack_modalert.log, a name the UCC alert base class hard-codes. Splunk_SA_CIM routes every*_modalert.logtocim_modactions, so with CIM installed the app's logs left_internal. It now logs toslack_alerts_alert.log.default/props.conf: theslack_alerts:logsourcetype for all the app's logs, with explicit line breaking, so tracebacks stay one event, and millisecond timestamp parsing.Fixes #70
Test plan
_internalasslack_alerts:log, nothing new goes tocim_modactions, a multi-line traceback indexes as one event, and_timematches the raw timestamp.