Questions tagged with Amazon CloudWatch

The docs for Cloudwatch pricing are clear about what will incur costs. However, where can I view statistics on volume of logs ingested by cloudwatch and other metrics? I would like to know when I have used up or am close to using up the free allocations.lg...

After combing through docs, I see that CloudWatch can accept custom statsd metrics with the correct configuration (adding the `statsd: {}` property to the config object). However, I am unsure how to send those metrics from my Elastic Beanstalk app to CloudWatch. There doesn't appear to be a built-in way to do that. If this needs to be manually configured on the EB side, can someone please point me to some documentation?lg...

I have a function that uses `putLogEvents()` method and it works fine locally but not when we push it out to our server (EC2 instance). We are always getting 504. I checked our LB and its allowing all traffic. I am running out of ideas why it is timing out on our server.lg...

I need to generate an event in order to a microservice can proseced it. That event must be generate from aws cloudwatch alert. ¿How can I implement it?lg...

I can't get the ARN for metric that is in the cloudwatch.lg...

Hi, I've deployed a custom model container as Sagemaker Async Endpoint which works fine so far. It's callable and provides results as expected. I now want to apply a TargetTrackingScalingPolicy but some of the metrics specified [here](https://docs.aws.amazon.com/sagemaker/latest/dg/monitoring-cloudwatch.html#cloudwatch-metrics-endpoint-invocation) seem to be not reported, they're also not visible in CloudWatch, e.g Invocations and InvocationsPerInstance. On the other hand, metrics like ModelLatency, TotalProcessingTime and TimeInBacklog show reasonable values. I guess due to these values missing e.g. applying this policy config doesn't have any effect either: ``` TargetTrackingScalingPolicyConfiguration={ "TargetValue": 2.0, # The target value for the metric. - here the metric is - SageMakerVariantInvocationsPerInstance "CustomizedMetricSpecification": { "MetricName": "InvocationsPerInstance", "Namespace": "AWS/SageMaker", "Dimensions": [{"Name": "EndpointName", "Value": endpoint_name}], "Statistic": "Average", }, "ScaleInCooldown": 60, "ScaleOutCooldown": 60 }, ``` Thanks a lot for any advice!lg...

I need to create a single alarm for cpu utilization >70%, memory utilization >80% and disk utilization > 60% for all my EC2's. How to achieve this using a single lambda function and this function need to use ec2 tags to associate instances.lg...

 I checked CloudWatch and found that the Volume Bytes Used metric suddenly dropped around 700GB without any cause, I'm the only one authorized to run queries in the company on a live environment and I didn't run any Any query like "delete" or "drop" the table/data at the time of this drop, can anyone who has encountered this situation explain it to me?lg...

Hi, I'm running EC2 instances. I want to get CPU usage by lambda function. But I haven't been able to figure out what should I write with JSON to configure Lambda function. I want to ask if you can show the example codes for lambda function. and I want to get this CPU utilization by everyday and every month. And also possibly Disk usage and memory usage too.lg...

I have a lambda triggered by a SQS FIFO queue when there are messages on this queue. Basically this lambda is getting the message from the queue and connecting to QLDB through a VPC endpoint in order to run a simple SELECT query and a subsequent INSERT query. The table selected by the query has a index for the field used in the where condition. Flow (all the services are running "inside" a VPC): `SQS -> Lambda -> VPC interface endpoint -> QLDB` Query SELECT: `SELECT FIELD1, FIELD2 FROM TABLE1 WHERE FIELD3 = "ABCDE"` Query INSERT: `INSERT INTO TABLE1 .....` This lambda is using a shared connection/session on QLDB and this is how I'm connecting to it: ``` import { QldbDriver, RetryConfig } from 'amazon-qldb-driver-nodejs' let driverQldb: QldbDriver const ledgerName = 'MyLedger' export function connectQLDB(): QldbDriver { if ( !driverQldb ) { const retryLimit = 4 const retryConfig = new RetryConfig(retryLimit) const maxConcurrentTransactions = 1500 driverQldb = new QldbDriver(ledgerName, {}, maxConcurrentTransactions, retryConfig) } return driverQldb } ``` When I run a load test that simulates around 200 requests/messages per second to that lambda in a time interval of 15 minutes, I'm starting facing a random long execution for that lambda while running the queries on QLDB (mainly the SELECT query). Sometimes the same query retrieves data around 100ms and sometimes it takes more than 40 seconds which results in lambda timeouts. I have changed lambda timeout to 1 minute but this is not the best approch and sometimes it is not enough too. The VPC endpoint metrics are showing around 250 active connections and 1000 new connections during this load test execution. Is there any QLDB metric that could help to identify the root cause of this behavior? Could it be related to some QLDB limitation (like the 1500 active sessions described here: https://docs.aws.amazon.com/qldb/latest/developerguide/limits.html#limits.default) or something related to concurrency read/write iops?lg...

Hello :wave: We are trying to use Cloudwatch Logs together with Cloudwatch Log Insights to Query through application's logs and visualise the API usage by different consumers. A single log consists of fields such as: - consumer (api user) - controller (base endpoint on which the consumer made a request) - action (exact action on which someone sent a request) Sample entry could look like this (obviously it truncated for the sake of explaining the problem) ``` { consumer: 'test-app-1', controller: 'api/test-controller', action: 'test-action } ``` Now, I would like to find a way in which I can group this in a line chart, for example requests made to different controllers by the consumers over time or exact action requests by consumers over time. I am not sure how to write the query, if I am to be honest, as ``` filter @logStream = 'someLogStream' | fields @timestamp, @message | stats count() by consumer, controller, action ``` does not generate a line chart over time, and adding ``` filter @logStream = 'someLogStream' | fields @timestamp, @message | stats count() by consumer, controller, action, bin(15m) ``` does not change the error message on visualisation screen, which states that: >The data is not suitable for a line chart. Try a bar chart, or group your result by bin function. Can anyone advise on what should I do? For starters, requests over time per consumer would be a nice metric and I believe that once we get to that point, we will be able to modify it per action / per controller. I think that I lack proficiency in the Insights syntax to achieve what I want. Thanks!lg...

I am trying to plot a line chart for mem_total vs mem_used for all my ec2s in a single widget. I need this chart to be dynamically updated (when the instance is terminated and new machine comes up it should be able to identify and update). Currently i am using metric explorer widget where I get mem_used and mem_total as separate line charts. I want to have mem_total vs mem_used in a single line chartlg...