Monitoring AWS Services
Did you know that LogicMonitor currently has support for over 70 AWS Services? As we add more coverage for services be sure to update to ensure coverage. For a list of services that we currently monitor please visithttps://www.logicmonitor.com/support/cloud-resource-units,25Views16likes0CommentsAWS Gateway Load Balancer monitoring functionality must be added.
Hi LM Ihadarequestfromoneofourclientstosetupmonitoringandalertingforthegatewayloadbalancers,butIcouldn'tfindanydocumentationonthat,andaccordingtoLMsupport,thefunctionalityisn'tcurrentlyavailable. I'dliketorequestyoutopleaseintegratethisfunctionalityassoonasyoucan. Please refer the awsGWLB's documentation below. https://aws.amazon.com/elasticloadbalancing/gateway-load-balancer/35Views10likes2CommentsDoes anyone aware where I can find AWS cloud watch API call logs in AWS account or from LM?
Does anyone aware where I can find AWS cloud watch API call logs to collect metrics from LM account like cloud watch or cloud trail? I wanted to know how many API calls made to the aws ec2 service for a particular ec2 instance in given time to collect metrics.Solved76Views10likes3CommentsAWS EC2 cloud collector vs local collector
Hi, When we add our AWS account to LM, Bydefault AWS EC2 instances are monitored via cloud collector. I have a local collector installed on AWS environment and I have made the device to monitor via local collector rather than cloud collector. But even after changing the collector still I can see metrics are polled every 5 mins in the cloud collector data source which will get the metrics from cloud watch. I want to know if this will increase our cloud watch cost for my account.Solved82Views10likes1CommentLinux details for EC2 hosts
Linux details for EC2 hosts such as Kernel version, etc are not displayed, as the Linux_SSH datasource specifically excludes these. I can understand that for some hardware specific properties/info, but it would be useful to have the patch release, etc. of the kernel regardless of being a VM/EC2 in AWS. Is there another datasource or property source I should be using for this info?39Views9likes3CommentsMonitoring 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.61Views7likes1CommentCloudwatch custom datasource metric path including wildvalue
Hi, I have created a cloudwatch custom datasource to pull custom metrics from cloudwatch by following this document -https://www.logicmonitor.com/support/lm-cloud/getting-started-lm-cloud/5-adding-monitoring-custom-aws-cloudwatch-metrics We got a scenario where we are pulling custom metric for a AMQ broker in cloudwatch. So we created a datasource for that,While creating datapoints(where metric path is specified) we like to include wildvalue in that. metric path we looking to create - pulling CPU utilization metric for different brokers. Where ##wildvalue## is placed with Broker Name. AWS/AmazonMQ>Broker:##wildvalue##-1>CpuUtilization>Average AWS/AmazonMQ>Broker:##wildvalue##-2>CpuUtilization>Average When wildvalue is replaced with Broker Name - “prod-1”.. Metric path should look like below. AWS/AmazonMQ>Broker:prod-1-1>CpuUtilization>Average AWS/AmazonMQ>Broker:prod-1-2>CpuUtilization>Average By this way we can reduce number of datapoints created a datasource, also we can use that datasource for multiple devices. So could someone please provide suggestion on this. Thanks.,24Views6likes0CommentsAWS Lambda Alias
GX2WXT A single Lambda function might have several versions. The default Lambda datasource monitors and alerts on the aggregate performance of each Lambda function. Using the Alias functionality in AWS, this datasource returns CloudWatch metrics specifically for the versions to which you have assigned aliases, allowing you to customize alert thresholds or compare performance across different versions of the same function. This datasource does not automatically discover aliases and begin monitoring them (as this could very quickly translate into several Aliases being monitored and drive up your CloudWatch API bill). Instead, add only the Aliases you want monitored by adding the device property "lambda.aliases" either to individual Lambda functions or at the group level if you're using the same Alias across several lambda functions. To add more than one, simply list them separated with a single space - e.g: "Prod QA01 QA02". If an alias does not exist, no data will be returned. This datasource is otherwise a clone of the existing AWS_Lambda datasource with the default alert thresholds.0Views2likes1CommentUpdated 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.0Views2likes5CommentsHow many collectors do you have?
Hello, Our Logic Monitor environment is overloaded. What is the best practices to expand? We have currenty 64 collectors “All the same size” and ourinternal LM Support for the collectors is requesting 52 new collectors!! They are taking the approach to create collectors all the same size for 10,000 instances. I was thinking about other routes 1. bigger collectors if possible for 30,000 instances each may be... 2. minimize the number of instances by cleaning up what is not needed but I am not sure anybody will know We have an AZURE Collector VZPOHIALGCMON01 with 82,305 instances !!! I reviewed this Collector Capacity | LogicMonitorand apparenlty we could expand another way than the one selected !!! Any thoughts on this? Thanks, Dom103Views2likes2Comments