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.,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?AWS 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/LogicMonitor has expanded its relationship with AWS for unified monitoring and cloud coverage.
LogicMonitor hasexpanded 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.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 or5 minutes.How 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, Dom
Can anyone here confirm CloudWatch metrics are working?
Is your CloudWatch data coming through? Ours stopped working days ago We just discovered all of our CloudWatch metrics are no longer showing up in LM starting at about 18:00 UTC on Feb 28th. I have confirmed that this is also reflected in our Cost Explorer - which indicates that the data is no longer being requested (or that the requests are failing for an unknown reason). We have several Org accounts and they appear to all be impacted. I wasn’t able to confirm with LM Support whether or not we are the only impacted customer so I’m soliciting anyone here for feedback. Cloudwatch API calls are not logged by CloudTrail, which severely limits our ability to diagnose the issue on our end. We are, however, reasonably sure that there were no changes made by us that would cause such a catastrophic loss of monitoring data. There is currently an issue shown onhttps://status.logicmonitor.com/but it does not accurately describe this issue. Any replies would be very helpful. Thank you in advance.
