Joe_Tran
AdvisorJoined 9 years ago
User Profile
AdvisorUser Widgets
Contributions
Re: Use AWS Unified Cloudwatch Agent to replace Logic Monitor Collector in multiple AWS accounts
What's your appetite for increasing your CloudWatch costs and some DIY scripting? You would just need to configure the CloudWatch agent to submit system metrics and DIY something to submit anything it doesn't do out-of-box as a custom metric. With LM Cloud, an add-on module, the cloud collector can fetch any CloudWatch metric, custom or otherwise, as long as the Datapoint metric path can be constructed without much logic. As for RDS MS SQL Server instances, with LM Cloud, you do have access to the CloudWatch metrics. You can install a collector on an existing app server (one that already talks to the database) to perform custom queries/assign custom datasources. The last option is to deploy the collector like an agent (e.g. nano or small sized). I wouldn't recommend it though. This was a management nightmare for us but granted this for an on-premises customer and they were very strict as to what we were allowed to do. YMMV.0Views0likes0CommentsRe: add api access to portal upgrade status
?... LogicMonitor's StatusPage allows for webhook integrations. Something can be designed to consume (or scrape) those events . This would necessitate LM to post their planned maintenances, which they do not do. @LogicMonitor --- is there a reason why planned maintenances and portal upgrades are not announced on StatusPage?0Views0likes0CommentsRe: How to monitor a curl call with cert and key
Looking at the innards of the service-detector.jar, which is where I think the canonical LMRequest class is defined, you won't be able to do this with an internal web check (scripted or out-of-box) as documented. You would be able to do this with a scripted Datasource though--something similar to this:https://stackoverflow.com/questions/21223084/how-do-i-use-an-ssl-client-certificate-with-apache-httpclient. The libraries listed in the SO threadsolution (except for junit, which isn't necessary) are availableto the current GA collector. I have not attempted to use the apache httpclient libraries in a scripted internal web check... yet. So if you feel adventurous?...2Views1like0CommentsRe: Monitor arbitrary TCP port
I had DIY'd a scripted Groovydatasource ages. Not sure if this was exactly what PortMulti- did, but the results should be similar. (host, port) = "##WILDVALUE##".split(':') try { s = new Socket(host, port.toInteger()) s.close() return 0 } catch (ConnectException ce) { println ce.toString() return 1 } catch (BindException be) { println be.toString() return 4 } catch (NoRouteToHostException re) { println re.toString() return 2 } catch (PortUnreachableException pe) { println pe.toString() return 3 } catch (Exception e) { println e.toString() return 5 } You would just then setup a datapoint to capture the exitCode and alert if it was > 0.15Views1like0CommentsRe: URL Provided in Alert based on DataPoint
Assuming you leverage and consume custom alert messaging, you can define the KB article at the datasource template level. Taking your CPU utilization example, go to your CPU datasource LogicModule, and add the URL to the custom alert messaging for the desired datapoint triggering alerts. If the KB is different for different subset of resources, then the alert messaging should be updated to reference a custom property that would be assigned to or inherited by the resource. Example ##CPU_KB_URL##, then you would assign/inherit the cpu_kb_url property to your different subsets of resources. This does mean you will have to maintain these properties in LM.0Views1like0CommentsCloud 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.1View0likes1CommentRe: add step failure description to website alerts
We have website-Overall trigger critical alerts and individual test locations trigger errors. I have toyed with the idea of a script that scrapes our ticketing system's API (ServiceNow) for website alerts, query the LM REST API for the alert message from the one/all error level alerts for that monitor object, and add that"context" to the ticket. We're pretty heavy in AWS so this would be all done via one or more Lambda Functions. Biggest downside--this is asynchronous.1View0likes0Comments