2 Answers
- Newest
- Most votes
- Most comments
1
I think this issue has been solved. It was ultimately a configuration problem with the agent, which wasn't immediately evident from the agent's own log file, but was revealed in /var/log/messages. Once this problem was corrected, the CWAgent namespace began appearing on the CloudWatch console page.
answered 2 years ago
0
See if this link helps. It talks about procstat plugin and how to collect metrics using the same
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-procstat-process-metrics.html
answered 2 years ago
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked 2 years ago
- asked 7 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
Sandeep, thanks for the reply. Yes, that is the doc page I am referring to; at the bottom it makes mention of choosing the CWAgent namespace, but I don't see where that can be done on the CloudWatch console page, and none of the new stats are appearing in the list of per-instance metrics for this instance.
As far as I can tell, all indications of the agent on the instance itself (such as the agent log) are normal.