Getting Data In

Splunk add-on for New Relic -- Getting Error : ValueError: No JSON object could be decoded

jdedev
New Member

Hello All,
Trying to setup Splunk add-on for New Relic and getting this errors in the logs :
ValueError: No JSON object could be decoded

return _default_decoder.decode(s)
File "/opt/splunk/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/opt/splunk/lib/python2.7/json/decoder.py", line 382, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2020-02-05 07:09:20,410 INFO pid=19395 tid=MainThread file=connectionpool.py:_new_conn:758 | Starting new HTTPS connection (1): 127.0.0.1
2020-02-05 07:09:21,302 INFO pid=19395 tid=MainThread file=connectionpool.py:_new_conn:758 | Starting new HTTPS connection (1): 127.0.0.1
2020-02-05 07:09:23,247 INFO pid=19395 tid=MainThread file=connectionpool.py:_new_conn:758 | Starting new HTTPS connection (1): 127.0.0.1
2020-02-05 07:09:25,140 INFO pid=19395 tid=MainThread file=setup_util.py:log_info:114 | Proxy is not enabled!

Lookin at the logs using this request
index=_internal newrelic sourcetype="splunk_ta_new_relic_new_relic_account_input-too_small"

Any help is much appreciated.

Regards,
Serge

Tags (2)
0 Karma

felixwawolangi1
New Member

Hi,
I had the same issue recently.
From 14th of Jan, the add-on stopped ingesting Alerts/Violation data and throwing 'ValueError: No JSON object could be decoded' errors.

Turns out that the 'Servers' API is deprecated, and if this is selected in the inputs ('API Key'), the add-on just errors out.

Try disabling that API in your input.

Regards
Felix

0 Karma
Register for .conf21 Now! Go Vegas or Go Virtual!

How will you .conf21? You decide! Go in-person in Las Vegas, 10/18-10/21, or go online with .conf21 Virtual, 10/19-10/20.