Browse through the questions and answers listed below or filter and sort to narrow down your results.
2
answers
0
votes
13
views
asked 18 days ago
1
answers
0
votes
9
views
asked 18 days ago
2
answers
1
votes
21
views
asked 23 days ago
Possible to editing alarm name and delete created metrics in Cloudwatch
Hi!
I'm trying to do a bit of clean up in CloudWatch, but I run into some problem. I'm still a newbie at Clouwatch so I'm hoping there are some easy answers to my questions. Having said this, I'm quite surprised why what I try to achieve seems to be hard.
**1. Is it not possible to edit an alarm name?**
When I go into edit mode of an already created alarm, I can edit the Metric name that the alarm is based on, but not the actual alarm name itself (step 3: Add name and description). That input box for the name is greyed out, i.e. readonly. Since all alarms appear in a list and there is no possibility as far as I know to have tree view hierarchy in this list, you do want to group alarm names in order to get some kind of overview and hierachy to find an alarm you are loking for. To me, it seems like the choice has been made under the CloudWatch hood to make the name of the alarm act as the programming identifier, i.e. not editable. Why?
**So my question boils down to: is it only possible to edit the alarm name by deleting the alarm and recreating it?**
**2. Some metrics seem impossible to delete**
When I was new to CloudWatch I accidentally created several different namespaces for the same namespace (mistyped). So I need to clean up and move some metrics from one namespace to another. To move a metric from one namespace to another does not seem possible, so I recreated the metric with the correct namespace name. But now I find that it is impossible (?) to delete the old metric with the old incorrect namespace. If I use the menu option "Metrics -> All metrics" I'll get an overview of all namespaces under the browse tab. But there is no way I can see to delete neither the metric, nor the faulty namespace they reside in in this view. How do I achieve this? If I go into the main LogGroups view, there is a column "Metric Filters" in the grid that shows a link to the metrics attached to each LogGroup. But the metrics with faulty namespaces do not appear anywhere which may be because the old log group they were based on may have been deleted. If so I guess they were deattached from the parent LogGroup and no longer accessible? So why were they not deleted when the LogGroup was deleted (cascading delete) and why is it not possible (?) to delete a parentless LogGroup if so?
Accepted AnswerAmazon CloudWatch
3
answers
0
votes
9
views
asked 23 days ago
0
answers
1
votes
6
views
asked a month ago
Bucket transfer inter-region
I need to transfer files between regions AWS. Bucket South America to Bucket in North Virginia with DataSync.
My files in South America region (source), are in S3 Deep Archive, and I'm going to keep them that way, I'm just going to change regions to reduce storage costs. In the AWS documentation, I understood the costs of DataSync, but about the Deep Archive I was in doubt... I have many files with less than 180 days (300TB), I will pay pro rata for taking them out of the bucket before this deadline or for I keep in the same storage class just transfer the files to another location, no? Because I want to make this change but if you have a pro-rata payment, it's a very high cost.
Accepted AnswerAmazon CloudWatch
1
answers
0
votes
5
views
asked a month ago
Fetch multiple couldwatch metrics in one cli call
Hi, how do I retrieve multiple metrics of ec2 instance in a single aws cli call? I want to retrieve cpu, writeops, readops etc for an ec2 instance, but instead of of issuing multiple aws cloudwatch get-metric-statistics calls for each metric, is there a way to get data for all metrics in one call?
```
aws cloudwatch get-metric-statistics --metric-name EBSWriteOps --start-time "2022-04-18" --end-time "2022-04-19" --period 60 --namespace AWS/EC2 --statistics Average --dimensions Name=InstanceId,Value=$id --output text --query 'avg(Datapoints[*].Average)'
aws cloudwatch get-metric-statistics --metric-name CPUUtilization --start-time "2022-04-18" --end-time "2022-04-19" --period 60 --namespace AWS/EC2 --statistics Average --dimensions Name=InstanceId,Value=$id --output text --query 'avg(Datapoints[*].Average)'
```
Can above 2 calls be combined as one call?
Accepted AnswerAmazon CloudWatch
1
answers
0
votes
6
views
asked a month ago
0
answers
0
votes
0
views
asked 2 months ago
How to rename Name in Namespace on Cloudwatch All Metrics
Hi AWS,
Please help me change Name in Namespace on CloudWatch All Metrics. I have config CloudWatch agent push metrics from EC2.
This is an evidence image: https://postimg.cc/HJ25Zfz1
This is my configuration
```
{
"agent": {
"metrics_collection_interval": 60,
"run_as_user": "root"
},
"metrics": {
"namespace": "DEV/EC2",
"append_dimensions": {
"AutoScalingGroupName": "${aws:AutoScalingGroupName}",
"InstanceId": "${aws:InstanceId}",
"InstanceType":"${aws:InstanceType}"
},
"metrics_collected": {
"disk": {
"measurement": [
"used_percent"
],
"metrics_collection_interval": 60,
"resources": [
"/"
]
},
"mem": {
"measurement": [
"mem_used_percent"
],
"metrics_collection_interval": 60
}
}
}
}
```
Thank All.
Best regard.
Accepted AnswerAmazon CloudWatch
2
answers
0
votes
11
views
asked 2 months ago
CloudWatch Alarm Metadata in notifications
Is it possible to include metadata about the source of a CloudWatch alarm in onward notification to SNS?
I'm working on a multi-account configuration hosting various services and plan to integrate with a third party notification and ops toolset. It would be very helpful to let operational teams receiving notifications know more about the alarm (e.g. source account, service, environment). The only fields I can see are name and description, these could be used but are unstructured so may be prone to error. Another solution would be to have multiple SNS topics, but ideally operational teams would manage any categorisation in their ops tool rather than making changes to infrastructure.
Any suggestions appreciated. Thanks.
Accepted AnswerAmazon CloudWatch
1
answers
0
votes
6
views
asked 2 months ago
0
answers
0
votes
2
views
asked 2 months ago
1
answers
0
votes
9
views
asked 2 months ago
1
answers
0
votes
14
views
asked 2 months ago
2
answers
0
votes
81
views
asked 3 months ago