I have installed the Splunk O11y agent via linus script. I have the smartagent/rabbitmq receiver/pipeline per the instructions at https://help.splunk.com/en/splunk-observability-cloud/manage-data/available-data-sources/supported-i...
Whicle restarting the service and viewing logs, I see a failure:
Jul 11 14:40:06 ip-1**-**-**-**.ec2.internal otelcol[3749684]: 2025-07-11T14:40:06.105Z info collectd/logging.go:41 configfile: stat (/usr/lib/splunk-otel-collector/agent-bundle/run/collectd/global/managed_config/*.conf) failed: No such file or directory {"resource": {"service.instance.id": "418ee031-25d8-4d3c-a115-6fb7e98c4992", "service.name": "otelcol", "service.version": "v0.128.0"}, "otelcol.component.id": "smartagent/rabbitmq", "otelcol.component.kind": "receiver", "otelcol.signal": "metrics", "name": "default", "collectdInstance": "global"}
Since the instructions do not mention this directory/.conf files, I would expect these to have been installed by default. Does anybody else have experience with this?
Also, just a note: The RabbitMQ developers have deprecated the http api in favor of prometheus, and while the agenbt has the capacity to build promehteus receivers, the
Hi,
It's probably worth noting that message is "info" level and not actually an "error". It's mostly just annoying. That directory is managed at runtime so even if you put placeholder files in there, they would get automatically deleted.
As a heads-up, there is movement away from the smartagent receivers in favor of native OTel receivers as they become available. You may want to try the OTel rabbitmq receiver instead:
https://help.splunk.com/en/splunk-observability-cloud/manage-data/available-data-sources/supported-i...
@bishida thanks. The URL you linked was the one I used and lists smartagent. Is there a different URL?
Oops, yes, I meant to share this one. It's a native OTel receiver (as opposed to a smartagent receiver)
Also, if I vreate the directory /usr/lib/splunk-otel-collector/agent-bundle/run/collectd/global/managed_configs/ and stick the collectd.config in there, if I restart the service the directory is removed.
Dicing deeper, I saw that the collectd.conf had an Include line at the bottom of the default config. I wound up commenting this out. ¯\_(ツ)_/¯