Shack

Members
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    2

Community Reputation

6 Neutral

About Shack

  • Rank
    Observer

Recent Profile Visitors

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

  1. We have an issue with our Cisco ASR's. The entPhysicalEntry returns the main chassis SN along with all of the other installed modules SN's. The problem is that it's setting the SN of a module other than the main chassis. This then syncs back to our CMDB with the wrong SN. Have any of you guys encountered this? The excerpt below is from a custom prop source we have but is also included in the main Device_BasicInfo prop source. // entPhysicalEntry def seenOidTypes = []; def entWalk = Snmp.walk(hostname, ".1.3.6.1.2.1.47.1.1.1.1"); entWalk.
  2. Click on property sources then select a property source(any of them) then in the URL put 21 at the end and hit enter. That will take you to property source 21.
  3. 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.
  4. Thanks Mike. I have a ticket open on the issue already and we actually had to roll back on Friday.
  5. 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.
  6. Yes we are using the official integration from the app store.
  7. 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.
  8. 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.
  9. 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
  10. 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 mis
  11. 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.
  12. 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.
  13. 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
  14. 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 esx.host & .pass in addition to SNMP? I'm not having much luck getting them to pick up any of the vCenter DS's
  15. It would be nice if ConfigSources were available to add to the device inventory report.