Vitor Santos

Members
  • Content Count

    130
  • Joined

  • Last visited

  • Days Won

    24

Everything posted by Vitor Santos

  1. Thank you Stuart. I'll share this post with our CSM. Regards,
  2. 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!
  3. Do I need to submit a feature request? Or what's the proper action here (since I already have this post)?
  4. 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),
  5. 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
  6. In the past I also had that need & what I ended up using (from debug console) was !aplist & !apdetail commands. !aplist -> refer to help !aplist for further info This will return a list of the tasks ran against different hosts (on the collector context). From there, you can extract the task ID: With that ID you can run the !apdetail <id Here> & it'll return you the details of that run (if it discovered new props, failed, etc...) Not pasting all the info here since it contains sensitive info for us. Related with the time it ran I didn't found
  7. Yeah, just confirmed and that works. Passed the actual collector on the wild value of the !posh script context and it rebooted as expected Example command -> shutdown /r /f /t 0
  8. Hello Stuart, I was able to query the API on past Monday. Went further and developed all the DataSources we need (to mimic the SNMP monitoring). I would like to publish those into exchange but I'm not quite sure how. Tried to publish those into my repository but the window just keeps stuck on the loading phase for one of the DS. Perhaps you could give me some advise on how to do that. Those might be helpful for another folks or even for you guys to review it.
  9. Just a thought, you could extract those properties from API response & map those into the discovered instances (as auto.* props) - example auto.service auto.currentstatus etc... From there you could map the ones you feel important & if generating an alarm you could invoke those same properties on the alarm custom message itself (it could be useful) - example Service '##auto.service##' is degraded.... Not sure if it makes sense to you. Just suggesting it because I did it this way a few days ago when creating a DS that reads from the device Event Fault table (I
  10. Ok, I finished the datasources we need & I believe it looks nice. Deployed those within all the Tegile devices & it seems to work nice. I was trying to create a package out of those (to further deploy it within Exchange) but, Exchange seems to be weird today. I can't even commit those to our rep. Anyone else facing issues?
  11. This look really nice. Does it still looks to 'not real-time' data from MS? I know there was a limitation in terms of data that API parses (since it was getting data indeed but, not real-time).
  12. Hello Michael, Thanks for you reply! I was able to do it in the meanwhile (started reading the documentation and trying out on Groovy) & ended up getting it. I'm working on trying to do the same monitoring (via API) that we're currently doing using SNMP (there's some limitations but, I believe we can do it). I'll post here my data sources once I've finished them (in order for you guys to view/correct/make use of).
  13. To start with I was looking for already existent data sources. Just wanted to understand if someone already had something, otherwise, I understand that will need to do it from scratch.
  14. Hello, I've been searching for Datasources related with Spanning Tree Protocol monitoring but didn't found one. Does this mean there's no out-of-box datasources for STP monitoring? This is extremly useful in terms of monitoring. Appreciate the feedback.
  15. From what I've read apparently it's mainly HTTP gets (replies in JSON 🙂) My issue is on creating a Groovy script for that (Java its not my thing). Thank you!
  16. Hello, We're monitoring a lot of Tegile device(s) via SNMP (making use of the OOB datasources, however, those fail quite often). This is happening for the majority of our clients & after our NOC opened a case with Tegile directly (they stated there's a bug when using SNMP on the MGMT IP). Having that in mind, I started leveraging the possibility of using Tegile API instead of SNMP. Searched through the Exchange but found none developed yet. My idea would be replace the SNMP with API ones. I've found their documentation about API calls but, actually requires some help to
  17. Hello, We're monitoring a lot of Tegile device(s) via SNMP (making use of the OOB datasources, however, those fail quite often). This is happening for the majority of our clients & after our NOC opened a case with Tegile directly (they stated there's a bug when using SNMP on the MGMT IP). Having that in mind, I started leveraging the possibility of using Tegile API instead of SNMP. Searched through the Exchange but found none developed yet. My idea would be replace the SNMP with API ones.I've found their documentation about API calls but, actually requires some help to pu
  18. It works smoothly! Just concerned with the load on the collectors (once we add a quite big expression) - Lets see how it goes Thanks a lot for you help Stuart!
  19. Nice to hear that! We'll start mapping our stuff & see if it works. Using a sample event (that I can trigger on purpose) in order to test this out. Will further update
  20. I've further checked the event table on the device itself & the date isn't the same (obviously ). I've raised a support case #208119 to engage support. Thank you for the availability!!!
  21. No problem!!! Ok I think I got that, within the 'Application' log we've multiple filters where we want to fetch events from multiple different sources & for each of those sources only grab specific IDs. Example (just using two events we get from the Application events): Both of those events fall into the 'Application' logs but contain different sources & different IDs per source. From looking into the Event Source definition I'm able to pass the Source(s) & ID(s) but, in a separate way: This will not restrict those IDs to the actual Source(s). Bu
  22. Ok so I've ran the groovy script in Debug console & tweaked it like this: It returned this: I see the first event is good & its no longer getting triggered because it already passed. However the second event still display the data wrongly & LM it triggering that alarm every 60 minutes (but duplicated) The event date I guess it could be a bug at the device (I'm thinking on raise a case with support anyway). However, related with the duplicated alarm, do you have any idea why?
  23. Okay... still kinda lost lol Can you provide an example?
  24. Hello, We've noticed the out of the box event source 'Liebert_Condition_Events' is triggering alarm where the actual date of the event is in the future (example below): NOTE: Blurred the device name (in order to protect our client information) I've already accessed the device in question & the system time is correct. Could this be an issue with the data source 'timestamp' handling? Or there's another thing that I might be missing? Thank you!