Missing critical metric on AWS RUM


Hello everyone!

The docs 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

질문됨 일 년 전310회 조회
1개 답변


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

However, as described on the AWS documentation, 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 command neither. You should use the get-metric-data or get-metric-statistics commands to retrieve it.

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

profile picture
답변함 일 년 전
  • I've confirmed that I still cannot find this metric in my console, nor using this command.

    I have been able to trigger errors and I see those ONLY in the RUM section of Cloudwatch console and not as a Metric and thus, no working alarm. Thanks for your help!

    aws cloudwatch get-metric-statistics --namespace "AWS/RUM" --metric-name "JsErrorCount" --start-time "2023-07-24T00:00:00Z" --end-time "2023-08-16T00:05:03Z" --period 3600 --statistics "Sum"

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인