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.,37Views6likes0CommentsLogicMonitor "Application ELB" Datasource returns NoData instead of metric for ELB 5XX
We have noticed "HTTPCode_ELB_5XX_Count” Datapoint from"AWS_Application_ELB” Datasource configured to collect"Raw Data” from AWS ELB following the Metric path "AWS/ApplicationELB>LoadBalancer:##system.aws.resourceid##>HTTPCode_ELB_5XX_Count>Sum” and whenever it detectsCloudwatch metrics has value, it returns value in Logicmonitor datapoint as well Example: (When Cloudwatch has metrics for 5XX, below displays in poll) HTTPCode_ELB_5XX_Count 18.0 (When Cloudwatch has empty/null metrics, below displays in poll) HTTPCode_ELB_5XX_Count NoData But after we resolve the5XX error, Cloudwatch metrics value will be empty/null in awsthat reflectsNoData for the Datapoint in LogicMonitor. Our Requirement: We should not get NoData even if the CloudWatch metrics empty/null Could someone please suggest a solution for this requirementSolved97Views4likes3CommentsDoes 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.Solved110Views10likes3CommentsDoes 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?Solved65Views11likes7CommentsTell 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!!20Views9likes0CommentsAWS 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.Solved127Views11likes1CommentCan 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.39Views1like1CommentIs 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?57Views1like3CommentsUse 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 Foley11Views1like1CommentDatasource for API Gateway Resources behind a stage
I have been using a custom datasource to collect the metrics for each resource and method (excluding OPTIONS) behind a API Gateway stage. It has been extremely useful in our production environments. I would share the datasource via the Exchange, but the discovery method I'm using will not be universal, so I think it would be best if that discovery were to work natively. If possible, could we please have a discovery method for AWS API Gateway Resources by Stage? *Something to note - This has the potential to discover quite a few resources and thus, create a substantial number of cloudwatch calls which might hit customer billing. For this reason, I added a custom property ##APIGW.stages## so that I could plug in the specific stages I wish to monitor instead of having each one automatically discovered. The Applies To looks like this: system.cloud.category == "AWS/APIGateway" && apigw.stages Autodiscovery is currently written in PowerShell (hence why not everyone can take advantage of it) $apigwID = '##system.aws.resourceid##'; $region = '##system.aws.region##' $stages = '##APIGW.Stages##'; $resources = Get-AGResourceList -RestApiId $apigwID -region $region $stages.split(' ') | %{ $stage = $_ $resources | %{ if($_.ResourceMethods) { $path = $_.Path $_.ResourceMethods.Keys | where{$_ -notmatch 'OPTIONS'} | %{ $wildvalue = "Stage=$stage>Resource=$Path>Method=$_" Write-Host "$wildvalue##${Stage}: $_ $Path######auto.stage=$stage" } } } }6Views0likes1Comment