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.,
Tell us about what you like about LM cloud
Hello everyone - this is Richard brooke, I am one of the member of the training team here at Logic Monitor. As we grow our collections of trainings and courses here at Logic Monitor, we like to get a feeling and feedback of what features, sets of features or combination that makes using the LMenvision platform positive. We are looking to add more to our cloud Knowledge repository and would like to hear from our users What do you like about LM cloud - What features or what makes it something to like? - Is there something that makes your day to day IT tasks better or easy? - Is there a feature or function that is the best thing since sliced bread and or beer in a can (Both are fantastic IMHO) Would love to hear some feedback here or ping me at richard.brooke@logicmonitor.com THANKS!!
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.Is it feasible to get data for EBS from CloudWatch metrics at every minute interval?
I'mseekingfordatathatwillreproduceCloudWatchdatainLMateveryminutefrequency,howeverI'monlygettingdataevery5minutes. Furthermorenotedintheglobaldefinitionis-GathersElasticBlockStorageperformancestatisticsassuppliedbyCloudWatch.AccordingtoAmazon,theminimumpollingintervalis5m. @Stuart Weenig - Is there any solution to solve this thing?Use AWS Unified Cloudwatch Agent to replace Logic Monitor Collector in multiple AWS accounts
Is there any way to use the AWS Unified CloudWatch Agent and Cloudwatch Logs load EC2 metrics into LogicMonitor similar to what is pulled from theLogicMonitor collector? A little background. We currently use two LogicMonitor collectors to gather Windows metrics from AWS EC2 instances and physical and virtual servers in our on-prem datacenter. This has worked well for the 100 Windows servers and network devices we are monitoring. We are moving all of our on-prem Windows applications to AWS, which requires we change the way we use AWS. Take a look at AWS Control Tower for more details Instead of one AWS account and one VPC ( network ) , we are moving every application and environment ( PROD, UAT, DEV, STAGE ) into different AWS account. No shared networking, so VPC peering or using a TGW isn't an option. This will result in about 20 new AWS accounts and up to 100 by the end of the year. Each of these accounts will have 2 to 20 EC2 Windows instances for web/application along with one EC2 or RDS based Microsoft SQL Server instance. I have no desire to pay for EC2 Windows instances for every account ( possibly hundreds ) just to run the LogicMonitor collector. The most important Windows server monitoring features we rely on in LogicMonitor boil down to - server is down ( ping loss ) - low disk space - high CPU utilization - the ability to alert on Windows Event log entries - Windows service X is not running Then tack on monitoring of an EC2 and RDS Microsoft SQL Server performance data Does LogicMonitor have any recommendations or examples on this type of configuration? Thanks in advance, Kevin Foley