Dave Lee Q

  • Content count

  • Joined

  • Last visited

  • Days Won


Community Reputation

3 Neutral

About Dave Lee Q

  • Rank
    Community Member
  1. Hi Mark, there is no documentation as yet on this, but there is a beta datasource that uses powershell in order to check for the health state, ReplayQueueLength and CopyQueueLength. In order to obtain a beta datasource you need to contact chat support who can import it for you, The datasource you want is called Exchange_DAG-..It uses remote Powershell so it may be that you are required to set your hosts up with remote Powershell in order to use this datasource. https://www.logicmonitor.com/support/datasources/powershell-support/using-powershell-scripts-in-logicmonitor/
  2. Jeremy, One way to do this is to write a powershell script that checks the time now, and if its between 1 a.m. and 2 .a.m runs the query, if not does nothing but report the values returned from the last time it ran. Incorporate this into a datasource and its only going to run the query at that time. You set the ds to run every hour, but it wont run the query until the right time. David
  3. Narr. I have replied to your ticket too. The global settings for timezones are in Settings>Account Information and the the portal settings tab.
  4. Agreed this would be very useful if at times you know collector XX has an issue with overloaded wmi tasks for example, you can quickly identify which alerts are caused by that.
  5. We would like the ability to add a text box widget shown per device at the device level to show information specific to that device Rather than have to rely on custom properties restricted to so many chars. Something like this
  6. Two very useful metrics to be monitoring on our EC2 instances are CPUCreditUsage : The number of CPU credits consumed during the specified period. This metric identifies the amount of time during which physical CPUs were used for processing instructions by virtual CPUs allocated to the instance. CPUCreditBalance : The number of CPU credits that an instance has accumulated. This metric is used to determine how long an instance can burst beyond its baseline performance level at a given rate. Close monitoring of these enable us to spot an error if a T2 instance is using more CPU than it should over time, monitoring CPU usage alone is not enough as once your credit balance is 0 the usgagae is throttled by amazon to a baseline level. In other words if your credit balance reaches 0, the cpu utilisation will drop to either 10,15 or 20% depending on the instance type, Making it impossible to alerts on cpu usage of 100%. AWS/EC2>InstanceId:##system.aws.resourceid##>CPUCreditBalance AWS/EC2>InstanceId:##system.aws.resourceid##>CPUCreditUsage Added these manually and they work fine, would be nice if these were included in the default logicmodule
  7. As Tom pointed out you need to add the hostname, but if you already doing this then the help page http://www.logicmonitor.com/support/monitoring/os-virtualization/troubleshooting-wmi/ has a section on repairing wmi counters. "You may be experiencing unexplained errors such as "Empty result set", ox80041003, 0x80041017 from the collector debug, WBEMTEST utility, or your custom application." There are steps to repair your counters in that help page, I have found this cures the empty results set problem in all cases I have seen. Microsoft state that this may happen when "... certain extensible counters corrupt the registry, or if some Windows Management Instrumentation (WMI)-based programs modify the registry", but the exact nature of these issues is largely unknown and normally not worth troubleshooting extensively.