Thank you, config is attached ... I've obscured the ip...    Here's the log    Apr 11 16:44:00  otelcol[142312]: 2024/04/11 16:44:00 main.go:89: application run finished with error: failed to resolve config: cannot resolve the configuration: cannot retrieve the configuration: configsource provider failed retrieving: yaml: line 91 : did not find expected key Apr 11 16:44:00 systemd[1]: splunk-otel-collector.service: Main process exited, code=exited, status=1/FAILURE Apr 11 16:44:00 systemd[1]: splunk-otel-collector.service: Failed with result 'exit-code'. Apr 11 16:44:01 systemd[1]: splunk-otel-collector.service: Scheduled restart job, restart counter is at 5. Apr 11 16:44:01 systemd[1]: Stopped Splunk OpenTelemetry Collector. Apr 11 16:44:01 systemd[1]: splunk-otel-collector.service: Start request repeated too quickly. Apr 11 16:44:01  systemd[1]: splunk-otel-collector.service: Failed with result 'exit-code'. Apr 11 16:44:01 systemd[1]: Failed to start Splunk OpenTelemetry Collector. ... View more

I am in fact using the Splunk Otel Collector and have validated the indentation. ... View more

Same comment here on the navigation. The new [list] view is much more cumbersome to traverse and the list does not have any tools to order or choose columns to include/exclude. Also, the detector are nice to have, but if no detectors are linked or enabled, there is a lot of real-estate lost on the page view..  Perhaps just having the summary line with severity/counts and it be the hyperlink to the active alerts may reduce some of the space used. The tiled Dashboard group and related dashboard (same as the [all dashboards] view) was a much cleaner/simpler view at the team level ... View more