Keimond

Members
  • Content Count

    16
  • Joined

  • Last visited

  • Days Won

    2

Community Reputation

3 Neutral

About Keimond

  • Rank
    Observer

Recent Profile Visitors

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

  1. Sorry @GraphTheWorld, not ignoring you! My priorities in the company have been shifted elsewhere right now and D42 isn't one of them. I'll come back and elaborate more later.. (I've also asked the rest of my team to give their input on what they'd like to see) At most, our top goal was, whatever is in Device42 labeled as production should be in LogicMonitor (unless monitoring is set to off) .. or/and the opposite.. whatever is in LogicMonitor should be in Device42.
  2. @Sarah Terry Thank you !!! That helps out a lot, that answer doesn't seem to be very straight forward for the common user. Especially when an alert is cleared. The user has to know then if they want to go see history on an instance that when they go to the alerts tab on that instance, they also have to change cleared to all to see past alerts then click on history. -- which is why a tab right next to alerts might be nice, or a visible "history" button under the alerts tab so that the common user can easily have a link to see history. At least for now it's just a matter of training everyone
  3. hey @Sarah Terry I was just search for "history" and ran across this.. I was just looking at a resource and thinking boy it would be nice if right next to the Alerts tab was a History tab (or maybe it could just show on the same Alerts tab as old alerts... basically a quick way to see has this instance alerted before and when ? Which would be great for the normal user!
  4. Just another random note lol.. I read YAML better so I'm always using https://www.json2yaml.com/ name: test111 parentId: 111 appliesTo: startsWith("system.displayname","Prod") translates to { "name": "test111", "parentId": 111, "appliesTo": "startsWith(\"system.displayname\",\"Prod\")" } *shrug*
  5. long post.. I'm posting this more as an informational; this is what we did to collect everything through snmp rather than open up any ports like ssh... If you have ideas on making it better I'm all ears! Nothing fancy.. I modified the code from the real world example that snmp pass_persist gives on their page... the main script loads stuff from a YAML config file then calls each python module, passing the snmp pass_persist object (pp) and config object over to them. The modules will run a quick test to see if they actually need to run... for example if the machine doesn't have DNS, then t
  6. So I see LM has provided a sample integration script for iTop.. (https://github.com/logicmonitor/lm_python/tree/master/examples/itop-sync) I'm curious if anyone out there has taken this example and created something for Device42 that they wouldn't mind sharing ?! I plan on trying to start something in a month or two, mind you I am by no means much of a programmer