You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to send alerts to Slack the alert will never send it to Slack. This began after the upgrade to Splunk Cloud
Version: 9.2.2403.108 Build: 918af2204023. I believe it might be related to Python which I believe was upgraded from version 2 to version 3.
09-11-2024 03:33:32.232 +0000 INFO sendmodalert [2987359 AlertNotifierWorker-0] - action=slack - Alert action script completed in duration=168 ms with exit code=1
Describe the bug
When attempting to send alerts to Slack the alert will never send it to Slack. This began after the upgrade to Splunk Cloud
Version: 9.2.2403.108 Build: 918af2204023. I believe it might be related to Python which I believe was upgraded from version 2 to version 3.
A list of the errors is below:
09-11-2024 03:33:32.232 +0000 WARN sendmodalert [2987359 AlertNotifierWorker-0] - action=slack - Alert action script returned error code=1
09-11-2024 03:33:32.232 +0000 INFO sendmodalert [2987359 AlertNotifierWorker-0] - action=slack - Alert action script completed in duration=168 ms with exit code=1
09-11-2024 03:33:32.224 +0000 FATAL sendmodalert [2987359 AlertNotifierWorker-0] - action=slack STDERR - Alert action failed
09-11-2024 03:33:32.224 +0000 INFO sendmodalert [2987359 AlertNotifierWorker-0] - action=slack STDERR - Slack API responded with HTTP status=200
09-11-2024 03:33:32.224 +0000 INFO sendmodalert [2987359 AlertNotifierWorker-0] - action=slack STDERR - Using configured Slack App OAuth token: REDACTED
09-11-2024 03:33:32.224 +0000 INFO sendmodalert [2987359 AlertNotifierWorker-0] - action=slack STDERR - Running python 3
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Send the alert to Slack
Screenshots
See above for errors
Splunk Environment:
Client Environment: (if it's a UI issue)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: