Michael Rodrigues

LogicMonitor Staff
  • Content Count

    130
  • Joined

  • Last visited

Community Reputation

102 Excellent

1 Follower

About Michael Rodrigues

  • Rank
    Thought Leader

Recent Profile Visitors

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

  1. You can't change the Host Dead time, it's hardcoded backend logic. You can change the Host Status alert but I don't recommend it, as it doesn't change the back end logic for host death and suppression. The only magic is the heartbeat interval on the HostStatus DS. It doesn't get reset by every collection type, for example SCRIPT modules will not reset it. Ping will. The backend looks at this value to determine host death and suppression.
  2. We are targeting Q1 2021 for an official release of these. Please speak with your CSM if you're amenable to letting us develop and test against your gear.
  3. We're targeting Q1 2021 for an official release of the beta stuff that's floating around. If you have Rubrik devices we can develop and test against, please reach out to your CSM.
  4. It's possible to write DataSources in any language your collector will execute today with Upload Script. We are looking at an official release of these Rubrik modules in Q1. If you can provide a device for us to develop and test against, please reach out to your CSM.
  5. @Vitor Santos we'll certainly improve Collector search when that page gets the "new UI treatment", but there's currently no plan to change how it's working in the current/old UI.
  6. Hey @Vitor Santos, it was changed in v140 as part of a bugfix. The page didn't support pagination, so users with enough Collector Groups weren't able to see them. We reused another similar component that already had paging, but it also changed the behavior to still show those empty groups. We can look into hiding those empty groups again when filtering.
  7. @Jeet_G we cover Synology and QNAP out of the box. If you have another system, creating SNMP-based DataSources to monitor it is generally pretty simple.
  8. @mnagel there's no SQLite JAR in there, unfortunately, but EA collectors do have a new script cache feature: https://www.logicmonitor.com/support/collectors/collector-configurations/collector-script-caching The cache is scoped to a device, and entries will survive collection intervals.
  9. The extended alert tuning stuff is still closer to 6 months out, but we're finding more areas where it will solve problems, and we're getting lots of asks for it, so the timeline could change.
  10. Awesome stuff @mnagel, they've all passed Security Review. Thanks for sharing. The monitoring team gives me gruff about the tech notes limit too. We have an item to bump the field length, but there is a decent amount of stuff ahead of it. The monitoring team actually wants to have something like Github README pages in the LMX, maybe at the package level. They write all the docs in Markdown before passing them to the Documentation team.
  11. @Vitor Santos, looks like their API uses Basic Auth, so it should be fairly trivial to make simple calls with our built-in HTTP library, and parse the JSON with JSON Slurper: import com.santaba.agent.groovyapi.http.HTTP import groovy.json.JsonSlurper hostname = hostProps.get("system.hostname") port = hostProps.get("api.port") user = hostProps.get("api.user") pass = hostProps.get("api.pass") httpClient = HTTP.open(hostname, 443, true) httpClient.setAuthentication(user, pass) /* * This helper function handles any HTTP GETs. */ def httpGET(endpoint) { httpClient.get(endpoint)
  12. @ray.tremayne you should be able to do this without the API with a counter or gauge type datapoint that you multiply by ##POLLINTERVAL## in a Complex Datapoint. Counter and Derive take the difference of current and previous and divide by the polling interval in seconds. You might get some slight rounding, but in most cases this should be fine.
  13. @kman looks like useful stuff! If you publish it to the Exchange and share the locator here I can get it through security review for you. Thanks for contributing!
  14. Hey @Vitor Santos, glad to hear you got this working. Sorry about the NX-OS stuff overlapping. I'm pretty sure we lack UCS C coverage via the API because we had no UCS C devices to develop it against. If you have UCS C devices you'd be willing to let us develop against, let us know what you'd like to see and we can see about getting it into an upcoming sprint.
  15. CollectorDB is an unpublished internal class/API. We are looking at building this functionality into a published API that you can use without fear.