Michael Rodrigues

LogicMonitor Staff
  • Content Count

    117
  • Joined

  • Last visited

Community Reputation

100 Excellent

1 Follower

About Michael Rodrigues

  • Rank
    Authority

Recent Profile Visitors

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

  1. 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.
  2. CollectorDB is an unpublished internal class/API. We are looking at building this functionality into a published API that you can use without fear.
  3. This behavior is a vestige of the original design, which was meant to handle SNMP tables that would reorder the entries: Value > Alias .0 > Foo .1 > Bar -reboot- -active discovery- Value > Alias .1 > Foo .0 > Bar So the alias persists, but the value changes over time. The value is used when reporting the data, because SNMP generally uses those index numbers to lookup related info in other tables. This has been carried all the way through to batchscript collection where the key/value pair output looks like ##WILDVALUE##.key_name. I'm fairly certain ##WILDALIAS##.key_name will fail, even if you build the output correctly. One nice thing is, all modules released within at least the last 4 years, generally generate unique wildvalues anyways, so at some point, I could see adding a toggle to each DS that just allows us to indicate a behavior change: "Wildvalue is unique/static". This would indicate that the collector should use the wildvalue to uniquely identify a given instance, and would allow us to handle the case where a name was updated (as we could confidently differentiate it from an actually new instance). Totally understand the frustration about some of the nuts and bolts stuff, and it's stuff that occasionally hamstrung me as a Monitoring Engineer. Maybe surprisingly, we don't hear a lot of complaints about this behavior. Filling out a quick feedback request in your portal, or via your CSM, will help me make the case to get this improved
  4. It will automatically pull in wmi.user/pass. Here are some recent javadocs: https://www.logicmonitor.com/support-files/javadocs/28606/com/santaba/agent/groovyapi/win32/package-summary.html
  5. @Jason_LMADM can you give it another shot? They were marked Private as part of our migration and got missed when we flipped all the locators in the forums back to Public. Thanks.
  6. @mnagel it's through review. Our system isn't smart enough to notice that we've reviewed an identical script. It just flags anything with code for review (including Groovy CDPs). It would be nice to check them against a list of previously reviewed code and possibly bypass SR in that case.
  7. Over the weekend I released a package of 4 SNMP DataSources for pf on OpenBSD. The package is called "OpenBSD PF". There are modules for general status, counter tracking, state table statistics, and traffic by label.
  8. Awesome. Passed Security Review.
  9. Hey @mnagel, I think I found the issue. Your if statement in the collection script checks to see if $TargetUser matches "wmi.user". Unfortunately, tokens behave differently in collection than AD. In AD, a nonexistent property will return the token name. In a collection script, a nonexistent property will return a blank string. I think if you change your collection script to match on "" for user and pass, it will work. I'll talk to the collector team about how we might be able to fix this and make things consistent.
  10. @Matt631 I missed NFTHXG originally, but it's set to Public now.
  11. @mnagel this module is out of code review now, thanks for the contribution.
  12. @mnagel we're actually putting tinyradius in the next EA (29) collector line. It should be available towards the end of June or the beginning of July.
  13. @Matt631 I toggled this one back to public. I will look into the others. Our intent was to flip anything to private if it was previously shared here. Thanks!
  14. Hey @mnagel we didn't have the concept of Private vs Public back then. We switched everything to "Private" unless it was shared on this forum, out of an abundance of caution. You can go toggle it to "Public" in the My Repo tab (must use card view to see the toggle for now).
  15. @Vitor Santos how would you see this working like DataSources given that PropertySources don't show up in the resources tree? Would you want a screen somewhere (for Resources, Resource groups) that shows which PropertySources are applied to resources in that section of the tree? that you could then toggle/untoggle?