LogicMonitor has expanded its relationship with AWS for unified monitoring and cloud coverage.
LogicMonitor has expanded our alliance with AWS, this lets IT and CloudOps teams confidently migrate with reduced risk, and oversee their post-migration estate on a unified platform. In addition to our partnership upgrade, our AWS monitoring capabilities have been significantly upgraded as well. Here are some of the highlights we announced at the AWS New York Summit. Fast and easy to get started Control cloud costs Migrate confidently Scaling and adapting to your AWS deployment Read the full article here.
AWS Gateway Load Balancer monitoring functionality must be added.
Hi LM I had a request from one of our clients to set up monitoring and alerting for the gateway loadbalancers, but I couldn't find any documentation on that, and according to LM support, the functionality isn't currently available. I'd like to request you to please integrate this functionality as soon as you can. Please refer the aws GWLB's documentation below. https://aws.amazon.com/elasticloadbalancing/gateway-load-balancer/Linux 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?Monitoring 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 or 5 minutes.Cloudwatch 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.,
