For example, our aws account xxxxxxx-data-dev we have enabled the custom metric for the AWS/FSx service. We have enabled/created the following QOS
aws.log errors:
Jun 21 08:10:09:733 [Data Collector - xxxxxxx-pcs-tst, aws] PERF: START: Sending qos for monitors
Jun 21 08:10:09:733 [Data Collector - xxxxxxx-pcs-tst, aws] no value found for monitor "ESC:SIMPLE_STORAGE_SERVICE:xxxxxxx-pcs-tst::S3::xxxxxxx-pcs-tst-2-alb-logging-us-east-1-bucket-adm"."NumberOfObject" on parent idsProbe:xxxxxxx-pcs-tst::S3::xxxxxxx-pcs-tst-2-alb-logging-us-east-1-bucket-adm
Release : 20.3
Component : UIM - AWS
Upgraded to 20.3.3 June 2021 Release and aws custom QOS issues were resolved