• Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

4 Neutral

About Shack

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In our environment we have a mixture of thin and thick provisioned datastores and my problem is that all of the ones that are thick provisioned immediately trigger the percent used thresholds set on the datapoint. Have any of you tinkered with splitting out thin vs thick into 2 datasources? I'm looking for ideas. Thanks.
  2. Thanks Mike. I have a ticket open on the issue already and we actually had to roll back on Friday.
  3. Anyone else running this version yet and having issues with collector restarts/crashes and then spamming of false alerts due to the restarts? It can't just be me.
  4. Yes we are using the official integration from the app store.
  5. Tested this today and have it working perfectly except I'm not getting a clear update sent to my ticket. Time to dig in a bit more.
  6. We do that too. Just black hole the alerts to go nowhere then when the client is ready remove them from the alert rule. I will definitely test out the clear state when I have some time.
  7. I see what you are saying with the custom DS that would always be in an alert state if present. I could use the same applies to that I have setup on my dynamic groups like you mentioned. Then the DS pops up on the device, alerts and then would be removed upon resolution of the problem. When the DS is removed would that send an alert clear? I need a clear sent out to our ServiceNOW integration. As for minimal monitoring - I have a dynamic group that's built around the same logic mentioned in that topic but it's just a group. Didn't know someone had a DS designed around it but now I'm going to take a look at it more. Appreciate your suggestions!
  8. I want to alert on something I fear I am going to have to do manually via reporting. My goal is to be able to alert on devices that are missing certain datasources. For example - Lets say you add a Dell server into your portal, WMI looks good, everything checks out and monitoring of Windows begins. Now lets say you forgot to setup SNMP for Open Manage and the Dell Datasource never pops up under this server. How can I alert on that? Right now I've been able to build out dynamic groups using the auto.activedatasources which will get me these lists. I have a group for Dell's missing the Dell DS, one for HP's missing the HP DS, another for SQL Servers missing the Database DS but I would like to be able to alert on these as opposed to relying on a dynamic group or report. Can this sort of thing be done?
  9. I get asked about this a lot as well. Some devices report uptime via this widget, some don't. Most don't. It would be nice to be able to hide/remove it entirely.
  10. Has this been considered? It would be 1000% helpful in our CMDB efforts if every resource had a consistent method to set system.sysname independent of the communication method to the resource(ESX, API, SNMP, WMI) etc.
  11. By applying these to system.categories on my PSC's I was able to get everything I need w/o having to create any new datasources. snmpTCPUDP,snmpHR,snmpUptime,VMwareSNMP,snmp
  12. Are any of you all able to monitor these? Specifically I am looking for CPU, MEM, Volume Usage. What DS's are you using and are you passing & .pass in addition to SNMP? I'm not having much luck getting them to pick up any of the vCenter DS's
  13. It would be nice if ConfigSources were available to add to the device inventory report.
  14. If you choose to use a netscan and want to rename your devices to the system name using ##SYSTEMNAME## the device must respond to SNMP first. The problem is LogicMonitor uses WMI exclusively for Windows, SNMP exclusively for most network equipment and vmware's api for hosts. So in my case I do not have SNMP configured everywhere. Now lets say you are scanning 5 full /24's and they put these devices in your portal. Now I am stuck having to go to the info tab on each one, locate the system.sysname(if present) and then click on Manage and rename the device. With 5 full /24's this a massive amount of devices to have to manually touch. Netscans have to be able to use the default method of connecting to each device and then ##SYSTEMNAME## must come from that depending on the device it is trying to connect to. Making us rely on just SNMP is not feasible.
  15. I want system.sysname populated by passing esx.user and esx.pass. Today that property is only passed if SNMP is configured on the host but it must be available by querying esx with the passed credentials.