1 Answer
- Newest
- Most votes
- Most comments
0
Hello, thanks for reaching out!
Unfortunately it's not possible at this time to configure multiple namespace destinations within a CloudWatch Agent metrics configuration, even when appending multiple config files with separate namespaces in the metrics sections.
There is a feature request in place for this ability, however, I'm unable to give an ETA on when this feature might be implemented for the CloudWatch Agent. You can keep an eye on the AWS What's New page for updates.
For the time being, the metrics from an Agent configuration will all have to utilize the same namespace. For increased ease of tracking these metrics, you do have the option of appending custom dimensions to each metric. Example:
{
"metrics": {
"append_dimensions": {
"AutoScalingGroupName": "${aws:AutoScalingGroupName}",
"ImageId": "${aws:ImageId}",
"InstanceId": "${aws:InstanceId}",
"InstanceType": "${aws:InstanceType}"
},
"metrics_collected": {
"Memory": {
"measurement": [
"% Committed Bytes In Use"
],
"metrics_collection_interval": 60,
"append_dimensions": {
"CustomDimensionName": "MemoryMetric"
}
},
"LogicalDisk": {
"measurement": [
"% Free Space"
],
"metrics_collection_interval": 60,
"resources": [
"*"
],
"append_dimensions": {
"CustomDimensionName": "DiskMetric"
}
}
}
}
}
Relevant content
- Accepted Answerasked 2 years ago
- asked 8 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago