Does 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?Solved65Views11likes7CommentsMonitoring Ec2 instances
Hi All, I have been going through the documentation and it suggests that when we are setting up monitoring for ec2 with autoscaling we should select netscan frequency of 10 minutes. This is the minimum time we can configure and new device may take upto 15 minutes to be monitored. My question is is there a way if a new instance is launched we can bring that into monitoring less than 10 or5 minutes.76Views7likes1CommentUpdated AWS EC2 ScheduledEvents
HCPFGA The default LogicMonitor datasource names the instances in a strange way and then alerts for events that have already completed. I've added a better instance naming convention that clearly identifies the event that will occur and when. I also put in logic to detect if the scheduled event has already taken place to prevent unnecessary alerting.8Views2likes5CommentsIssue 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.25Views2likes3CommentsTuning a collector to work on a t2.micro EC2 instance?
I know that it is not exactly recommended/reliable to use a 1GB/1CPU Core machine to monitor...but it seems that installing a "nano" sized collector on a t2.micro AWS instance and having it just monitoritself brings the AWS instance to a screeching halt. I am seeing that when the collector is running, top shows that CPU pegs to 100% almost nonstop. Memory is not hit quite as bad..but it does get up there to use 500mb+ But the CPU load average is 5+ cores and it makes the systemunusable. Sometimes this causes the instance to throwstatus alerts & even crash. Question: Has anybodybeen able to tweak the wrapper.conf etc files to make the collector CPU load less demanding?Solved5Views1like1CommentAdditional standard metrics for AWS EC2 logicmodule
Two very useful metrics to be monitoring on our EC2 instances are CPUCreditUsage :The number of CPU credits consumed during the specified period. This metric identifies the amount of time during which physical CPUs were used for processing instructions by virtual CPUs allocated to the instance. CPUCreditBalance :The number of CPU credits that an instance has accumulated. This metric is used to determine how long an instance can burst beyond its baseline performance level at a given rate. Close monitoring of these enable us to spot an error if a T2 instance is using more CPU than it should over time, monitoring CPU usage alone is not enough as once your credit balance is 0 the usgagae is throttled by amazon to a baseline level. In other words if your credit balance reaches 0, the cpu utilisation will drop to either 10,15 or 20% depending on the instance type, Making it impossible to alerts on cpu usage of 100%. AWS/EC2>InstanceId:##system.aws.resourceid##>CPUCreditBalance AWS/EC2>InstanceId:##system.aws.resourceid##>CPUCreditUsage Added these manually and they work fine, would be nice if these were included in the default logicmodule9Views1like1Comment