Ray Scholl

  • Content Count

  • Joined

  • Last visited

Everything posted by Ray Scholl

  1. That was it - I have added both datasources (I did refresh this page). Thanks Steve!
  2. No, not so much (same error) - unless I need to logout/login
  3. This will surely help a lot of customers, thank you for that. You cannot add this at the moment - the import throws an error - any idea when it will be available (or similar functionality)? 503 : This LogicModule is currently undergoing security review. It will be available for import only after our engineers have validated the scripted elements.
  4. I will explain the request here as best I can in a written format but a visual would be simple. By example of FortiGate: We had a requirement to monitor the WAPs (the FortiGate can act as a Wireless LAN Controller (WLC) ) for reporting and performance. Depending upon the size of the firewall 1 through N WAPs can be authorized, configured, and monitored. These devices are visible through SNMP queries against the firewall and offer a rich set of information (CPU, memory, version, SN, model, client associations). Now to the feature - when we added the capabilities it became time consuming to first identify the OID and then repeatedly poll to pin down the elements. So, how about a "button" in the UI next to the OID to walk or poll and display the results? Additionally, how about offering the results and on that page an option to add them in this datasource? Look at the Forti AP definition for what we did and try to visualize the simplicity of having the UI trigger a poll on a device (through the associated collector) to make this a breeze.
  5. The addition of configuration backups in LogicMonitor has been a great feature for our support team and really helps streamline things. If you like to be aware of people making changes and retain version history is is wonderful, but we have an issue on some of the more modern devices. Many new devices are intelligent and have subscriptions that pull the latest IPS, AV, malicious IP address lists, etc. from the manufacturer. There is also a periodic re-hashing of encrypted information for added security and these are expected behaviors - NOT a config change. We developed our own config backup using SCP for the devices so no passwords are stored in LM either, but the key here is that a login event (human or automated) causes the config version to change. The suggestion I have is simple - there needs to be a way to ignore these updates (often multiple in a day) and simply key on the first few lines where the config version is referenced - #config-version=FWF60D-5.02-FW-build742-161129:opmode=0:vdom=0:user={redacted} #conf_file_ver=17742419038372504090 #buildno=0742 That conf_file_version (line 2 above) would be the trigger and ignoring everything else would be perfect. Thoughts welcome!
  6. We completed a new integration and after a lot of effort we discovered that the escalation "NEXT" performed the create but subsequently every n minutes a new ticket was created - the ACK also still needs to be performed. Ideally, we would want the escalation to create the ticket and acknowledge the alert. Perhaps the escalation then has a null destination until it clears (active alert) or some other method to avoid repetitive case creation? I had a thread with Desh on support - no suggestions on a workaround.
  7. We go to great lengths in order to add an alias or port name to all of the device interfaces. I was hoping (we had a customer request) that you could include that name/alias/description to the interface name on the reports (instance alias as a nickname or automatically populate the description field each time a discovery runs).