Splunk Search

Using diffent python version in external lookup

Marvin_Janzen
Observer

Hello,

I am trying to use a different python version for my external lookup. The global version is 3.7 and my custom one is 3.10

my /opt/splunk/bin contains both 3.7 and 3.10

 

In my transforms.conf i changed the python version:

[externallookup]

python.version = python3.10
 
However I am getting the following error:
Marvin_Janzen_0-1751457334078.png

 

When I use 

[externallookup]

python.version = python3.7
 
, it does not give the error. Also I am able to use the new python version, when I change the symlink from 3.7 to my 3.10 (for debugging)
 
But why doesnt it work when I set the python.version to pyhon.3.10?
 
Thanks in advance!
Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

python.version = python3.10 is not a valid setting.  Allowed values are default, python3, python3.7, or python3.9.  I don't know how you were able to add Python 3.10 to Splunk, but doing so does not change the validation of python.version settings.  I strongly recommend using only the versions of Python that ship with Splunk (3.7 or 3.9).

---
If this reply helps you, Karma would be appreciated.
0 Karma

Marvin_Janzen
Observer

Alright, thank you for your answer!

0 Karma
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!

Introducing ITSI 5.0: Unified Visibility and Actionable Insights

Introducing ITSI 5.0: Unified Visibility and Actionable Insights Tuesday, July 21, 2026  |  10:00AM PT / ...

Inside Splunk Agent Observability: Understanding Agent Behavior, Tokens & Costs

Inside Splunk Agent Observability:Understanding Agent Behavior, Tokens & Costs Thursday, August 06, ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...