Vitor Santos

Members
  • Content Count

    90
  • Joined

  • Last visited

  • Days Won

    12

Community Reputation

31 Excellent

3 Followers

About Vitor Santos

  • Rank
    Collaborator

Recent Profile Visitors

178 profile views
  1. I have updated the actual DS.. Realized that it wasn't getting data from the actual endpoint in context. I was running PS commands locally (so it was always retrieving data from the Collector ). I've re-wrote it in order to use 'Invoke-Command' & this way it seems to be getting data for each device in context. Updated the GitHub repo
  2. Updated the actual code since the task ExitCode was being output as Decimal & it's easier to present it as HEX on the actual alarm message. To accomplish that, I've added a function that makes use of LM API & maps a custom property at the instance level (this way we can then reference it in the actual alarm message -> converted to HEX). Hope it's useful for anyone
  3. Hello folks, We had a request from a client where he had the need to monitor some important scheduled task(s). While checking the documentation, we wanted to avoid the procedure on the actual 'Job Monitor' for scheduled tasks (since the clients is kind of harsh when it comes to make changes in their boxes, even if those represent no harm). Since we were only interested in the actual task return code (after its run), we've done a quick DS (powershell). Just sharing it here in case it's useful for anyone. GitHub repo -> Here For now, we're alarming on the actual task r
  4. Yeah, this is a feature that our teams are used (from our prev. tools). It was something they really insisted to have. Hope it works smoothly Thanks anyway Stuart!
  5. Hello, I was able to surpass this by making API requests on the script itself (by update custom properties at the instance level directly). We now have 2 properties at the instance level (ResourceState & ResourceConfiguration). From there every time the script runs updates both properties with the respective values. On the alarm message I'm now able to invoke those tokens (##ResourceState##, etc...) & reflect the values. Thank you!
  6. I appreciate your suggestion, however, it doesn't suit our case. The complex datapoint is being used to trigger the actual severity of the problem. In case it's a resource fault we want it critical, if it's only config we'll want error instead. However, the status that we would like to pass on the message itself can have a lot of values (from the simple datapoint itself). It can be 1,2,3,4,5,6,7,etc... In sum, we've 2 simple data points that can have multiple values (where >2 isn't healthy). But 1 overrides the other (in terms of the issue itself). That's why we came up wit
  7. Hello, We've a complex 'datapoint' on a DS that will alarm based on different 'simple datapoint' values. We've the 'resource actual state' & 'resource configuration state' datapoints & we'll throw a 'Critical' alarm if the 'resource actual state' == 1 , but, in case it's equal to 0 we'll observe the 'resource configuration state' and throw an 'Error' alarm if it's ==1. This is useful for us, because we can have a resource that's online but, facing configuration issues. Our goal is retrieve both those simple 'datapoint' values in the actual alarm message itself (on the co
  8. This would be really nice to have. We struggle on this, specially on Dynamic Groups that might contain devices (due to the previous category) that no longer should be there.
  9. We were able to surpass this by tweaking the way the output gets processed (on the groovy script): snmpGet = new SNMPCollector()._convertTime(Snmp.get(host, community, version, oid)); This was found by the user MNagel - thanks a lot man! From there I've tweaked our DS in order to add context/support to SNMPv3. Bear in mind that in order to use SNMPv3 (in this STP context) the user/group needs to have view for the 'vlan-' context (tested this only at Cisco devices for now). Found this on post below: https://community.cisco.com/t5/network-management/multiple-snmp-v3-command-to
  10. I was checking on this & we were able to come up with a script that analyzes different VLAN(s) - using the actual VLAN context. I believe it's working as intended, however, the actual output of the snmp.get (on the TCN OID - .1.3.6.1.2.1.17.2.3.0) it's being automatically converted into a readable date (which I don't want, I want the RAW value in ticks). Example of how it's been printed within LM groovy: If I do a get on the same exact OID (outside of LM) it'll output the actual raw value (in time ticks) - example below This is the script I've so far (I just need to s
  11. Thank you Stuart. I'll share this post with our CSM. Regards,
  12. About the API capabilities, just to add my thoughts to Stuart reply (which you should adopt in first place).I was requested to develop a few scripts that make use of LM. There's some features that aren't documented but, you can make use of your browser programmer tools in order to actually see the different API requests (on the GUI). That helped me a lot & I was able to code some calls that weren't documented (even making use of API v3). Bear in mind those aren't supported by LM but, they might help you if you've urgent needs (like they helped me). Thank you!
  13. Do I need to submit a feature request? Or what's the proper action here (since I already have this post)?
  14. Your logic is exactly what we want. To sum, exclude just one event (for a certain period only) & don't affect the others on the same ES. We could do that (creating 1 ES just for that event), however, this is something that we do really often (for our diverse clients). That's not an optimal solution for us in terms of monitoring management, otherwise, we'll need to be creating separate ES all the time (whenever a client requests it for a certain event - which happens often). We actually can do this in our Alert Console (since our LM is sending all the alarms to our SNOW instance),
  15. Hello everyone, We've multiple Event Sources setup (each one of them covers multiple events (different sources & event IDs). They're kinda in the same category but they cover different events (example Backup Related Events - within those there's multiple applications, event IDs, etc...). Our question here comes if we need to filter a specific event (within one of those Event Sources) on a specific period of the day. For example, ServerA is returning some events at 2AM EST but those are related with a scheduled job that occurs daily, one of our clients requested us to filter tho