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.7Views0likes6CommentsDimensionless 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?5Views0likes5CommentsAWS Service Health Eventsource - Report at AWS Device Group Level
Today we were flooded with hundreds of alerts in our alert dashboard. AWS was having an issue in the ap-southeast-1 region with launching new instances. The "AWS Service Health" datasource found this issue and then alerted on it for each instance & ebs volume we had in that region. That was too many alerts, especially since the issue wasn't with our existing devices in that region. I would like this alert to happen on the AWS Device Group itself - per region, so that we can know about it, but it won't generate an excessive number of alerts with the same exact information.3Views0likes4CommentsCloud 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.2Views0likes1CommentAWS - Top API calls by User
MZMPR6 Every 5 minutes, thisdatasource will query ElasticSearch for a list of the top 20 API callers as identifiedby the "userIdentity.sessionContext.sessionIssuer.userName" identity. This should return a list of users that are running under automation as opposed to user accounts. This will also return the number of calls that are being throttled by AWS as outlined here:http://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html Use this datasource to improve any code you have running in AWS that relies on API calls outside of cloudwatch. Suggestions on how to improve this datasource are welcome! We've already used it to find a number of issues and identify code that was not adhering to AWS's API request guidelines. To Apply this datasource, assign the property "CloudTrailES.URL" to your Elasticsearch instance that services cloudtrail log requests. The value of this property should be the search URL endpoint for that Elasticsearch instance (e.g. "https://search-cloudtraillogs-ABCDEFGHIJK12345.us-east-1.es.amazonaws.com/_search")2Views0likes0CommentsManually specify/edit autodiscovered AWS Services
Hello, At the moment, when you've added an AWS Account, it will showallthe services you've asked for (e.g.,allSQS queues). Is it possible to have a feature where you can select a subset of these queues after they are discovered? Clearly they are stored somewhere (via a datapoint's metric path:##system.aws.resourceid##), but there doesn't seem to be a way of changing them. Thanks.2Views0likes3CommentsTuning 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?Solved1View1like1CommentAnyone 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.1View0likes2CommentsMore AWS-centric options for Netscan via AWS (EC2) Method
- Token to name a device based on AWS tag - The ability to exclude devices based on region - All AWS tags should be imported/populated/inherited - Netscan should populate the system.aws.resourceid property instead of system.ec2.resourceid. The former is actually used by the default AWS_EC2 datasource. Probably moot if my third bullet is done.1View0likes1Comment