Alert Can't connect https, but can curl from collector
Got an issue where getting a status "5", can't connect on https-443 to a web server on AWS EC2. But can connect to httpssite from public browser and using curl from the collector, without issue. Running diagnostics through LM shows a timeout. The "Poll Now" data looks fine except Normal Datapoints shows errors. These errors cannot be confirmed.99Views0likes6CommentsDimensionless Cloudwatch Metrics
I've been creating datasources to collect our custom AWS Cloudwatch metrics as per the docs:https://www.logicmonitor.com/support/monitoring/cloud/monitoring-custom-cloudwatch-metrics/- mainly this is fine... However it can't cope with dimensionless metrics: " Namespace>Dimensions>Metric>AggregationMethod , where Dimensions should be one or more key value pairs" I've tried creating datapoints without a dimension but it returns NAN (probably because LM requires "one or more key value pairs" for dimensions). We currently use a Python script to collect most our custom metrics but it's resource intensive for our collectors and I'm trying to move away from it. Does anyone know of a way to use the 'AWS CLOUDWATCH' collector with dimensionless metrics?15Views0likes5Comments
Datasource 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" } } } }12Views0likes1Comment
Cloud Collector to Consume AWS RDS Enhanced Monitoring
It looks like someone in my org had enabled "Enhanced Monitoring" for several AWS RDS instances--a surprise, to be sure, but a welcome one . I would love Cloud Collector method that can consume this data and display it along side all other metrics we are collecting in LogicMonitor. Implementation should be relatively simple. In the discovery, presumably usingdescribe-db-instances, we would just need a system.aws* property for the "dbiresourceid" which can be used to get-log-events.11Views0likes1CommentAnyone else seeing clear-text credentials on their EBS volumes?
We're seeing top-level credentials in clear-text under our EBS volumes. I have not noticed this before so I suspect this is due to a recent saascontrollerupdate. For example: the snmp.community appears hashed out at the top of the page, and appears again at the bottom as "system.mmunity" and the value is in clear text. Other, very sensitive credentials are also displayed. I'm currently number 4 in the queue waiting to speak with a rep about this, but I wanted to see if anyone else is experiencing this. For obvious reasons, I won't be screenshotting this. I would urge everyone to check their accounts to see if they are seeing something similar.8Views0likes2CommentsUpdated 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.8Views2likes5CommentsAdditional standard metrics for AWS EC2 logicmodule
Two very useful metrics to be monitoring on our EC2 instances are CPUCreditUsage :The number of CPU credits consumed during the specified period. This metric identifies the amount of time during which physical CPUs were used for processing instructions by virtual CPUs allocated to the instance. CPUCreditBalance :The number of CPU credits that an instance has accumulated. This metric is used to determine how long an instance can burst beyond its baseline performance level at a given rate. Close monitoring of these enable us to spot an error if a T2 instance is using more CPU than it should over time, monitoring CPU usage alone is not enough as once your credit balance is 0 the usgagae is throttled by amazon to a baseline level. In other words if your credit balance reaches 0, the cpu utilisation will drop to either 10,15 or 20% depending on the instance type, Making it impossible to alerts on cpu usage of 100%. AWS/EC2>InstanceId:##system.aws.resourceid##>CPUCreditBalance AWS/EC2>InstanceId:##system.aws.resourceid##>CPUCreditUsage Added these manually and they work fine, would be nice if these were included in the default logicmodule8Views1like1CommentCustom CloudWatch Metrics without a host
We have some custom CloudWatch metrics we'd like to gather, display and alert on however, they aren't specific to any host or AWS resource. If we push application specific metrics into CloudWatch, we don't want them tied to any specific application host as hosts/instances can come-and-go. We push these metrics to CloudWatch without an associated EC2 / AWS resource and can see them in CloudWatch, but without an InstanceID, we can not pull these metrics into Logic Monitor. We'd like to be able to pull in and organize any metric from CloudWatch, regardless of whether or not its dimensions include an InstanceID etc.8Views1like3CommentsNetscan AWS Integration (IAM instance roles)
While setting up NetScan Policy and choosing AWS can we instead rely on the IAM instance role of the collector instance (when the collector is an EC2 instance running in AWS) instead of hardcoding AWS AccessKey/SecretKey in the Netscan policy? http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html5Views0likes1Comment
Tuning a collector to work on a t2.micro EC2 instance?
I know that it is not exactly recommended/reliable to use a 1GB/1CPU Core machine to monitor...but it seems that installing a "nano" sized collector on a t2.micro AWS instance and having it just monitoritself brings the AWS instance to a screeching halt. I am seeing that when the collector is running, top shows that CPU pegs to 100% almost nonstop. Memory is not hit quite as bad..but it does get up there to use 500mb+ But the CPU load average is 5+ cores and it makes the systemunusable. Sometimes this causes the instance to throwstatus alerts & even crash. Question: Has anybodybeen able to tweak the wrapper.conf etc files to make the collector CPU load less demanding?Solved4Views1like1Comment