• Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

33 Excellent


About Brandon

  • Rank

Recent Profile Visitors

989 profile views
  1. Hi @Stuart Weenig! Thanks so much for taking the time to look into this. I did discover some issues with my output and it's now properly formatted. But, unfortunately, it's still not changing the appearance of the icons. I suspect perhaps this is related to the combination of category and type. For example - the in order for the AWS EC2 icon to appear on an EC2 instance, the output would need to look something like this: {"rawERIs":[{"category":"","priority":2,"type":"AWS EC2","value":"i-a1b2c3d4e5f6g7"}]} Of course, this is only a theory. I have yet to find any d
  2. I've been playing around with topology mapping with some success. However, the icons displayed after the map is built are the standard IP and instance icons. I've modified my custom ERI propertysources to try to get them to display something other than these two icons, but the icons never seem to change. According to the LM documentation regarding these icons, I should be able to choose anything from the list: Has anyone successfully been able to get the map to reflect the icons above? For example, "predef.externalResourceType=AWS EC2" does not appear to do anything. Nor does
  3. Hi @Nicklas Karlsson and @Jonathan Hill, So you guys are running into an issue where the datasource isn't finding any instances. That's no good! The datasource uses remote Powershell commands from the Windows collector to the target server. I would probably start by using an RDP session to a collector and running the script from an elevated PS session. Before you run it, you'll need to modify the script to use whatever creds you have set up on that target server. For a quick test, just check to see if these two wmi calls return anything from the remote system: $hostname =
  4. Hi @John Biniewski, The alert thresholds are largely going to depend on how large your share are. You can set the alert threshold to something quite low like 10, and wait for an alert, but unfortunately, this is one of those times when you'll need to revisit your thresholds to determine what is normal for your environment(s). Wish I could be more help here.
  5. I have built a generic StatusPage.IO datasource to allow for monitoring the status of various services we use. Since so many companies are using, I figured it's a good idea to have a heads up in the event there is an outage with one of our many service providers. This has worked well as an early warning system for our service desk guys to know about issues before they start getting calls from end users. LogicMonitor actually uses StatusPage, but of course there are many, many others. Attached is a screenshot of the StatusPage data that we've collected from https://stat
  6. @Eric Singer - Any chance VMWare provided you with a KB that documents this as a known issue / bug? I'd like to provide as much context as possible to our ESX admins. Thanks!
  7. DO NOT comment out the applies to field on the datasource! This will remove all historical data - which I can only imagine most of us want to keep. You can disable the datasource by creating a device group (if you don't have one already) and populating it with all of the ESX hosts. Then, at the group level, select the alert tuning tab and uncheck the box next to the datasource. This disables polling and alerting, but allows you to keep historical data.
  8. Do the instances at least get discovered? If so, could you do a poll-now and shoot me the error? I'm curious as to what the issue is.
  9. Hey @George Bica! Did you get any of the other datasources to work?
  10. W9PN3Y I thought I had already posted this one, but regardless - here it is. This does not apply to any servers by default as it can be extremely noisy if you don't have it tuned. This makes an API call to solr to pull error and severe logs and then formats them so that LogicMonitor can understand them. Before applying this, it's not a bad idea to review those logs manually to make sure something isn't repeatedly triggering (as is common with SOLR). Still - it's helped us detect and diagnose a range of issues that would have otherwise been difficult to see.
  11. ANLX64 This monitors solr JVM stats via the SOLR API without the need to enable jmx. This datasource may not work on older solr versions as this particular API call was only recently introduced. Still, it should be very useful for monitoring the overall health of the JVM application.
  12. ZLPJP3 This datasource monitors the status of each solr collection without the need to enable JMX. It is done via batchscript and seems to be very efficient. The only alert set up is for cores that are recovering. Other alerts can be set up at your discretion. There are a few graphs included as well.
  13. 3Z32Z4 This datasource monitors a large amount of SOLR performance data for each SOLR collection/core. It is done via batchscript and appears to return data extremely reliably and efficiently. There are no alert thresholds set up as performance expectations may vary depending on usage. I've also set up basic overview and per-instance graphs. There are 65 datapoints here though, so I'm sure more can be added.
  14. R79DJL I'm not sure if this datasource was removed intentionally, but there was a datasource named "Windows_Cluster_Failover" that monitored for cluster failover events. We've been using this datasource, but we noticed that it triggered a false alarm last night which prompted me to go back and rebuild it. This datasource will monitor a Windows cluster for a failover event. If a failover is detected, it will be logged in the LogicMonitor's installation directory (Default is "c:/Program Files (x86)/LogicMonitor/bin/"). The datasource exits if certain calls fail altogether (to prevent fa
  15. Well, I had a few use cases come up for this, so I decided to take another crack at it. I think this is going to work out better for us than my first version: hostname=hostProps.get("system.hostname") my_query="Select Name, DisplayName, PathName from Win32_Service" def session =; import com.santaba.agent.groovyapi.win32.WMI def result = session.queryAll("CIMv2", my_query, 15); def exclude = ['ALG', 'AppVClient', 'COMSysApp','diagnosticshub.standardcollector.service', 'FontCache3.0.0.0', 'EFS', 'KeyIso', 'msiserver', 'MSDTC', 'Netlogon', 'NetTcpPortSharing', 'RpcLoca