Getting Data In

AWS CWAgent are not getting to Splunk

kongusuresh
New Member

Hi
I have configured my input files as follows to get the cwagent custom metrics but metrics are not getting to Splunk server.
Please help I am struggling with it.

[aws_cloudwatch://test-CWagent_cca2f8c6-b830-41c1-8703-f2f22781a174]
aws_account = ************
aws_region = **************
metric_dimensions = [{"InstanceId":["."]}]
index = *
****_cwagent
metric_names = ".
"
metric_namespace = CWAgent
period = 600
polling_interval = 3600
sourcetype = aws:cloudwatch
use_metric_format = false
statistics = ["Average","Sum","SampleCount","Maximum","Minimum"]
metric_expiration = 3600
query_window_size = 24

0 Karma

samsplunks
Explorer

Same problem, no solution found.

If it can grab AWS namespaces, why can't it grab Custom namespaces?

0 Karma

kongusuresh
New Member

It is not possible because the cwagent is part of our golden amu and we are some automated scripts to build the alarm and aws dashboard

0 Karma

amiracle
Splunk Employee
Splunk Employee

Why not use collectd or the Splunk UF to pull the metrics and send them directly without using the CWAgent? This way if you move instances to another cloud provider, the configurations transfer easily without having to re-write props / transforms.

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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...