All Apps and Add-ons

Why is there an error when using Splunk Addon For New Relic - Alerts?

skirven
Communicator

I am trying to use the Splunk Addon for New Relic v2.2.0, and I keep getting errors. I think the New Relic API has changed slightly, and I tried to edit the modalert python file, yet I'm still getting errors such as:

02-22-2022 04:52:01.962 -0500 ERROR sendmodalert - action=alerts_to_newrelic STDERR - NameError: name 'basestring' is not defined
02-22-2022 04:52:01.962 -0500 ERROR sendmodalert - action=alerts_to_newrelic STDERR - if isinstance(self.sid, basestring) and 'scheduler' in self.sid:
02-22-2022 04:52:01.962 -0500 ERROR sendmodalert - action=alerts_to_newrelic STDERR - File "/opt/splunk/etc/apps/Splunk_TA_New_Relic/bin/splunk_ta_new_relic/cim_actions.py", line 124, in __init__
 
We are on Splunk 8.1.7.
Thanks!
Stephen
Labels (2)
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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...