Missing critical metric on AWS RUM

Question

Hello everyone!

The [docs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM-metrics.html) describe the metric named `JsErrorCount`. We had set an alarm against this metric and found that it was not firing. Upon investigation, I now see that it is no longer showing in the metric browser, nor on the CLI result. Has this metric been renamed, removed or is this a defect? Are the docs out of sync?

Thank you for the help!
-Niko

Answer

Hi,

No, the `JsErrorCount` metric has not changed its name and is still available. I have attached an image that shows it.

![Enter image description here](/media/postImages/original/IMEOIZjbQ0RN6bKSRNHgWolg)

However, as described on the [AWS documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/viewing_metrics_with_cloudwatch.html), metrics that have not had any new data points in the past two weeks do not appear in the console, and they are not returned in the results of a [list-metrics ](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudwatch/list-metrics.html) command neither. You should use the [get-metric-data](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudwatch/get-metric-data.html) or [get-metric-statistics](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudwatch/get-metric-statistics.html) commands to retrieve it.

Could you check if with any of these commands returns the `JsErrorCount` value?

Missing critical metric on AWS RUM

Relevant content