All Apps and Add-ons

Python3.13 Warning for Addon Slack Add-on for Splunk

sgeorg31
New Member

Hello,

I am receiving a warning that Slack Add-on for Splunk (version 3.0.0) is not compatible with Python 3.13 as part of the upcoming Splunk Cloud upgrade.

A few things I have already checked:

  • The latest version available on Splunkbase appears to be 3.0.0 and I could not find a newer release.
  • In inputs.conf, the add-on uses:
 
python.version = python3
 
  • There is no explicit Python version restriction in app.conf or app.manifest.
  • The add-on includes relatively recent libraries such as splunk-sdk 2.1.0, splunktaucclib 8.0.0, urllib3 1.26.20, packaging 25.0, etc.

My questions are:

  1. Is this warning indicating an actual Python 3.13 compatibility issue within the add-on, or does it simply mean that the app has not yet been certified/validated for Python 3.13?
  2. Has anyone successfully run Slack Add-on for Splunk 3.0.0 in an environment using Python 3.13?
  3. Are there any known workarounds, patches, or compatibility checks that can be performed before the Splunk Cloud upgrade?
  4. If the add-on is not yet certified for Python 3.13, is there an expected timeline for an updated release?

Any guidance from Splunk or community members who have encountered the same warning would be greatly appreciated.

Labels (2)
0 Karma

kml_uvce
Motivator

Hi @sgeorg31 

I don’t think this means the add-on is broken. It mostly means nobody has validated or declared it for 3.13 yet. If you look at the Splunkbase page, compatibility is only listed up to 10.0, and it’s a Splunk Works app marked “Not Supported”, so it hasn’t been updated for 10.2.

From what I’ve read in the 10.2 notes, 3.13 comes in as an extra interpreter and 3.9 stays the default. Since your inputs.conf has python.version = python3, the modular inputs should keep running on 3.9 after the upgrade. The part that moves to 3.13 is Python code that runs through Splunk Web (custom REST endpoints and Mako templates). That’s where I’d look first.

I haven’t run this exact add-on on 3.13 myself, so I can’t say for sure. What I’d do before your Cloud upgrade:

  • Spin up a 10.2 test instance, install the add-on, and override the python version to 3.13 in local/inputs.conf. Let the input run for a few intervals and check index=_internal source=ta_slack_add_on_for_splunk for errors. Also click through the config pages, since that’s the UI/REST side.
  • Grep bin/ and the bundled libs for imports that 3.13 removed, like cgi, imghdr, telnetlib, pipes, crypt, and distutils (gone since 3.12). If nothing shows up, you’re probably fine.
  • Rerun the Upgrade Readiness app after that.

For a timeline, I doubt anyone here can give you one. The app page says it’s best-effort support through [email protected], and the code is on GitHub (splunk/ta-slack-add-on-for-splunk), so I’d email them and open an issue there. I’d also raise a support case so your Cloud team knows you’re using it before they schedule the upgrade.

If you do test it on 10.2, please post back what you find. I’m sure others will hit the same warning.

kamal singh bisht
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Kubernetes Alerts That Work Out of the Box with AutoDetect detectors in Splunk ...

A deployment rolls out slowly, one pod sits not ready for a few minutes, and whoever is on call gets an alert ...

Observability at Your Fingertips Directly From Splunk Platform—for Free

At .conf, we announced our roadmap to bring observability foundations to Splunk Platform. Bringing metrics and ...