Issue in auto refreshing EC2 properties
I’m encountering an issue with my Windows ASG group EC2 instances. Whenever a new instance is added, certain properties from a dynamic group—most notably “wmi.user” and “wmi.pass”—are applied. However, by the time the instance is registered in LogicMonitor, WMI isn’t immediately available because some automations are still configuring the WMI credentials on the host. A few minutes later, WMI starts working on the host, and I can successfully test it using wbemtest from the local collector. However, the LogicMonitor portal still shows that WMI is not responding. Interestingly, when I use the collector’s debug console and explicitly specify the WMI credentials, it pulls the information successfully. But if I don’t specify the credentials manually, it fails to work. The only way to resolve this is by manually running “refresh properties,” after which WMI starts working without making any changes. I’m trying to figure out if there’s a way to automatically force a properties refresh every 15 minutes to ensure everything works as expected without manual intervention.25Views2likes3CommentsDoes cloud watch API calls bound to Data Sources or Data points?
Hi All, I have an EC2 instance in my aws account. The instance is assigned to local collector in the same subnet to collect metrics. At the same time the Cloud watch data sources are also continue to collect the metrics. I was not able to completely disable the cloud collector data sources because we need some metrics. My question is if we uncheck some of the data points(e.x :CPUUtilization)in the EC2 data sources to stop collecting the metrics, will it reduce API calls to the Cloud watch? By this way if we can save some cloud watch cost from AWS side? Does cloud watch API calls bound to Data Sources or Data points?Solved65Views11likes7Comments