Getting Data In

Splunk Add-on for AWS - cloudwatch inputs.conf

mpopescutlpn
Engager

When adding Cloudwatch inputs for Splunk Add-on for Amazon Web Services using the UI, it appears that in the background, Splunk appends a UUID to the input definition created in inputs.conf under /splunk/etc/apps/Splunk_TA_aws/local

Example:

[aws_cloudwatch://account_455e6345-ea85-4303-ad60-00f544bf502a]
metric_namespace = AWS/Lambda
[...]
[aws_cloudwatch://account_455e6023-ba56-4303-ad60-00f544bf502a]
metric_namespace = AWS/ApplicationELB
[...]

For Cloudwatch inputs added via Splunk Web, Splunk is able to aggregate all the cloudwatch metric configurations under a single input
alt text

But when we generate inputs.conf with an automation program, appending a generated valid UUID at the end of cloudwatch input names, Splunk creates individual cloudwatch inputs in the UI

Using configuration files, how can we ensure Cloudwatch inputs for a single account are summarised in a single line in the UI, such as when added via UI ?

alt text

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!

Agent Mode Engaged! Enchaining Agentic Operations with Splunk AI Assistant 2.0

    Are you ready to transform how your team handles complex data requests? We invite you to our upcoming ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...