Splunk Observability Cloud

Health check extension shows "Server not available" after adding smartagent/jmx receiver?

New Member

I am using Splunk Distribution of OpenTelemetry Collector in kubernetes. Current solution is working just fine. But after I added section for the smartagent/jmx receiver with groovy script inside, healthcheck starts to show "Server not available" status.  Groovy script works, logs includes several

2022-11-07T11:12:14.730Z error subproc/core.go:114 Get result, and sent:0 {"kind": "receiver", "name": "smartagent/jmx", "pipeline": "metrics", "monitorID": "smartagentjmx", "monitorType": "jmx", "runnerPID": 42}

(I just added stderr to script)

There are not any other warn/errors in logs. Kubernetes just kills pod cause healthcheck.  My jmx config:

type: jmx
port: 9999
intervalSeconds: 2
groovyScript: |
def printErr = System.err.&println
ss = util.queryJMX("com.hazelcast:name=MAP_NAME,instance=*,type=IMap").first()
dims = [env_name: "NAME"]
output.sendDatapoint(util.makeGauge("hazelcast.map.size", ss.size, dims))
printErr("Get result, and sent:" + ss.size)

Tell me where and how to dig? 

0 Karma
Get Updates on the Splunk Community!

Platform Newsletter Highlights | March 2023

 March 2023 | Check out the latest and greatestIntroducing Splunk Edge Processor, simplified data ...

Enterprise Security Content Updates (ESCU) - New Releases

In the last month, the Splunk Threat Research Team (STRT) has had 3 releases of new content via the Enterprise ...

Thought Leaders are Validating Your Hard Work and Training Rigor

As a Splunk enthusiast and member of the Splunk Community, you are one of thousands who recognize the value of ...