Joe Tran

  • Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

25 Excellent


About Joe Tran

  • Rank
    Thought Leader

Recent Profile Visitors

954 profile views
  1. I've resorted to fetching this from the REST API via the /alert/alerts resource... no ideal. 😕
  2. 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 alread
  3. 🤔 ... 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?
  4. 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: The libraries listed in the SO thread solution (except for junit, which isn't necessary) are available to the current GA collector. I have not attempted to use the apache httpc
  5. I had DIY'd a scripted Groovy datasource 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()
  6. ... or Jenkins Shared Library.
  7. 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.
  8. 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 using describe-db-instances, we would just need a* property for the "dbiresourceid" which can be used to get-log-events.
  9. 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.
  10. Saw this article from Ars Technica pop up in my news feed 😶
  11. I was able to recently use the v2 REST API to clone dashboards. 1. HTTP GET your "template" dashboard via /dashboard/dashboards/{id} 2. Modify the "template" to suit your need for the new clone, and deleting the following keys: id, template, userPermission, shareable, (and maybe groupName and groupFullPath, I was cloning private dashboards, so these keys don't apply to my immediate use case) 3. HTTP POST your modified "template" at /dashboard/dashboards/{id}/clone *insert disclaimer about undocumented REST API features*
  12. Assuming this is for the website-Overall instance--I'll just leave these other posts about improving and providing better context for Website (formerly Services) alerting: I am guessing the issue is one of scoping. Both website-Overall and the individual test locations are treated as separate instances. LogicMonitor doesn't have a good mechanism for instances to share data and metadata. I have contemplated creating a job/script/function that crawls our ticketing system for Website alert tickets, polls the LM API for the message from the individual test location (which we p
  13. ... with exceptionStatus ORA-01013: user requested cancel of current operation That is all. 😅
  14. As I am sitting here, trying to explain to one of our internal partners, for what seems like the umpteenth time, on how to read an alert threshold expression from a ##THRESHOLD## token--it would be great if there were individual message tokens for each of the thresholds. Something like ##WARNINGTHRESHOLD##, ##ERRORTHRESHOLD##, and ##CRITICALTHRESHOLD## that should render the comparison operator and that respective threshold value, example--- This way, I can be more clear as to what this string of numbers actually mean in this type of fashion
  15. Our DevOps team is developing a Grafana solution and having a LogicMonitor plug-in would be great to have!