MemoryDB Missing Metrics

Hello.

Does your Amazon MemoryDB use Valkey?
"SuccessfulReadRequestLatency" is a metric added by Valkey, so I don't think it will be displayed if you are using Redis.
https://aws.amazon.com/about-aws/whats-new/2024/10/amazon-memorydb-valkey-cloudwatch-metrics-monitor-server-response-time/?nc1=h_ls

By the way, in my case, the metrics were able to be displayed by writing and reading several times with the redis-cli command below.

set memorydb-key "hello memory-db"
get memorydb-key

If you're unable to find the SuccessfulReadRequestLatency metric for MemoryDB in CloudWatch, there are a few things to consider:

1. Metric Availability: First, confirm that your MemoryDB cluster is actively processing read requests. The SuccessfulReadRequestLatency metric measures the total time taken by MemoryDB to respond to a read request, so if there are no read operations, this metric may not appear.

2. Metric Namespace: Ensure you're looking in the correct namespace. MemoryDB metrics are typically found in the "AWS/MemoryDB" namespace in CloudWatch.

3. Time Range: Check if you've set an appropriate time range in CloudWatch. If the metric hasn't received any data points recently, it might not show up for more recent time periods.

4. Permissions: Verify that you have the necessary permissions to view CloudWatch metrics for MemoryDB.

5. Metric Delay: There might be a slight delay in metric reporting. Wait for a few minutes and check again.

If you've confirmed all these points and still can't see the metric, it's possible there might be an issue with metric collection or reporting. In this case, you should:

1. Check the CloudWatch agent logs (if you're using the CloudWatch agent) for any errors related to metric collection.

2. Verify if other MemoryDB metrics are being reported correctly. If other metrics are missing as well, there might be a broader issue with metric reporting from your MemoryDB cluster.

3. Contact AWS support if you've confirmed that your cluster should be reporting this metric but it's not appearing in CloudWatch. They can help investigate any potential issues with metric collection or reporting for your specific MemoryDB cluster.

Remember, CloudWatch doesn't retrieve metrics from your applications directly; it only receives metrics that are sent by the services. If there's an issue with the metric not being published, it's best to check with the source service (in this case, MemoryDB) or AWS support for further investigation.

Sources
Troubleshoot missing data points in your CloudWatch metrics | AWS re:Post
Monitoring MemoryDB with Amazon CloudWatch - Amazon MemoryDB
Which Metrics Should I Monitor? - Amazon MemoryDB