• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Brandon

  1. I agree - it definitely adds a lot of flexibility for creating groups having all of the services listed as a property of the device. The only problem I see is that the list can be extensive. There might even be a character limit for the field, so for some servers, it might not actually populate the entire list. Mosh's idea to only include running services is a great idea. I had thought of that when I wrote the script originally, but decided against it in case services happened to be stopped for whatever reason (such as patching), right as the collector was performing an active discovery sw
  2. This will be something I will be implementing across the board, but it won't be listing all services. Instead, the output will only display relevant services to automatically detect the type of server. For example - using an if statement to decide that the server must be a Domain Controller because it is running Active Directory Domain Services, Active Directory Web Services, and DFS Replication. The output would then be something like "Server.Role=Domain Controller" or "Server.Role=[Application] Web Server".
  3. D4KEAM Monitors and graphs the performance of each DFS replication member. No default alerting.
  4. ML9PNG Monitors the status of all DFS and DFSR required services: DFS Namespace, DFS Replication, and DNS Client.
  5. XKJNGZ Uses Powershell to make WMI queries to get the current backlog file count for each outbound DFSR partner on each DFSR share. These queries can be expensive if the backlog is large, so the polling interval is set to 10 minutes. If there is no backlog, the script finishes quickly. No default alerting is set, but I would recommend adding a threshold to be notified of potential replication issues. NOTE* - The collector must be able to reach both DFSR partners and will use the same credentials to make the queries for both.
  6. Brandon


    T4WZC3 Initially I created this to monitor the status of DFS shares, but can be used on any Windows share. Monitors for the status as indicated by Microsoft's MSDN site here Graphs allow you to easily see the status over time.
  7. 3JELEP Discovers and monitors the performance of the RabbitMQ processes and alerts if a RabbitMQ node's processes are in a stopped state or restart.
  8. PAGA9W This is a standard healthcheck as outlined in the RabbitMQ API documentation. Returns a value of 1 if the healthcheck is passed and 0 if there is a failure. Runs basic healthchecks in the current node. Checks that the rabbit application is running, channels and queues can be listed successfully, and that no alarms are in effect. If everything is working correctly, will return HTTP status 200 with body: {"status":"ok"} If something fails, will return HTTP status 200 with the body of {"status":"failed","reason":"string"}
  9. 96D2GG A revamped version of the existing RabbitMQ Queue datasource with the following improvements: 1. Performance (the biggest difference) - instead of the collector gathering all stats for all queues for each polling period, and then parsing the data looking for only the queue it is looking to monitor, it makes a specific API call for the queue attached to the instance. This drastically reduces the collection time as well as the amount of strain on the collector itself. 2. Fixed datapoint "avgAckEgressRate" as it incorrectly pointed to the Ingress rate, which means the ingre
  10. I'm not sure where else to post this, but I wanted to make sure the LogicMonitor team takes another look at the apache solr datasources in the repository as they need to be scrubbed. Currently these datasources use applies to rules that seem to be very specific to one customer. Here is one example: contains(system.groups,"SEARCH/CHI/SLAVE/JOB") or contains(system.groups,"SEARCH/AMS/SLAVE/JOB") or contains(system.groups,"SEARCH/QTW/SLAVE/JOB") or contains(system.groups,"SEARCH/CHI/MASTER/JOB") or contains(system.groups,"SEARCH/AMS/MASTER/JOB") or contains (system.groups,"SEARCH/QTW/SLA
  11. 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.
  12. NZRCTG This datasource will automatically connect to your BigFix server and gather a count of the fixlets that need to be applied. This uses the BigFix REST API and requires the following device properties to be set: bigfix.url - The URL of your bigfix server (for example: "") bigfix.port - The bigfix API port (default is 52311) bigfix.user - Specify a read-only user with the proper rights as documented here: bigfix.pass - The password for the bigfix account you are using The datas
  13. Kudos! I actually noticed the same thing a few months ago - and like the lazy community member I am - I fixed it without actually submitting it in to the forums or sending it to LogicMonitor to have the repository updated. If I remember right, there was also something wrong with one of the datapoints as well - although that could have been the RabbitMQ datasource. I'm going to try to be better about getting these uploaded.
  14. It would be great if graphs could auto-scale using a logarithmic function so as to display data that tends to have wide variances. Currently, if one instance has an extremely high value, all other instances in the graph appear at the very bottom. A checkbox on the custom graph page should allow the graph to scale appropriately so as to keep that data visible.
  15. @Michael Rodrigues I created a separate datasource called ESX_VM_Health that actually monitors and alerts on the status of VMTools and a few other metrics. I only just submitted it today, but I'd actually like to see my datasource wrapped up into the default ESX_VM- datasource since they are both extremely useful. The datasource I submitted is also written in groovy, so you shouldn't have too much trouble merging the two since the collectors don't need any modifications to take advantage of the added data. Your team could probably make it more reliable as well, since my datasource will like
  16. MW7E2C Description: Monitors the health of each VM as reported by VMTools. How it works: Automatically applies to ESX hosts and adds each guest with VMWare tools installed as an instance. Polls for the status of the VMWare tools service, the vm's heartbeat, configuration issues, and up/down state. Doesn't alert on anything unless the VM is up. Appears to be quite reliable for detecting VM's that are unresponsive even though all other metrics appear normal. Alerts aren't triggered until after at least two datapoints to prevent false-positives. No graphs for this as it's pretty
  17. Monitors EBS volume IO burst credits (measured in Percentage) and triggers a warning alert below 10%. JAPZ69
  18. This datasource does not provide any monitoring or alerting data. Once applied, it will gather information pertaining to each drac-enabled blade in the Chassis. This is useful for inventory purposes. *Note - in order to use this datasource, you must assign the CMC login credentials to the CMC using the properties idrac.user and idrac.pass. Remember that both the username and the password are case-sensitive. Using the root account is NOT recommended. W96MYH
  19. WARNING - This propertysource pulls a list of all Windows services installed. This does not filter the services to only show running or auto-starting services. Useful for auditing, auto-grouping, and inventory. Example below Displays the a list of all installed Windows Services. auto.winservices [AeLookupSvc, ALG, AppIDSvc, Appinfo, AppMgmt, aspnet_state, AudioEndpointBuilder, AudioSrv, BESClient, BESClientHelper, BFE, BITS, Browser, CertPropSvc, clr_optimization_v2.0.50727_32, clr_optimization_v2.0.50727_64, clr_optimization_v4.0.30319_32, clr_optimization_v
  20. Useful for inventory, auditing, and auto-grouping. Displays the a list of all installed Windows Features separated by commas. Example below. auto.winfeatures [Active Directory Lightweight Directory Services, .NET Framework 3.5.1 Features, Telnet Client, Remote Server Administration Tools, .NET Framework 3.5.1, Role Administration Tools, AD LDS Snap-Ins and Command-Line Tools, AD DS and AD LDS Tools, Active Directory module for Windows PowerShell] WMN9DN
  21. Useful for inventory purposes. Displays the total number of CPU's, cores, and logical processors on Windows machines. Also provides a description of each CPU. Example below. auto.cpu.cores 4 auto.cpu.logicalcount 4 4 auto.cpu0.description Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz auto.cpu1.description Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz auto.cpu2.description Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz auto.cpu3.description
  22. Just a heads up - None of the LogicMonitor documentation mentions the ##POLLINTERVAL## token. I only found it by stumbling upon it being used in one of the datasources. I think this token could be extremely useful in a lot of situations. Updating the documentation should help get the word out to those of us looking for this feature.
  23. Thank you so much Annie - that is indeed great news! Do you by chance have any idea when this version is scheduled for release? I'm very excited to use this new feature as soon as possible.
  24. During the initial and periodic device auto-discovery tasks, there should be far more information stored about each device. This information should be easily accessible from the device information page and populated with data such as "Installed Programs", "Installed Features", "Running Services", "Domain Role", etc. This information could then be used to auto-group devices. For example, I should be able to create an auto-discover rule that automatically grabs all Domain Controllers based on the system.installedservices and system.installedfeatures categories. There is no reason I should ha