CSOAR-3800: Splunk integration failing on JLR #5803
Merged
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
mahendrak-sumo
requested review from
JV0812,
amee-sumo,
jpipkin1,
kimsauce and
mafsumo
as code owners
jpipkin1
approved these changes
Sep 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Purpose of this pull request
This PR fixes a timezone handling issue in the Splunk integration that was causing failures on JLR (Jaguar Land Rover). The changes refactor timestamp preparation and URL encoding to address specific compatibility problems.
Refactors timezone parameter passing from global variable to function parameter
Improves URL encoding by using explicit safe parameter for alert names
Select the type of change
Ticket (if applicable)
JIRA:
https://sumologic.atlassian.net/browse/CSOAR-3800