Steve Francis

LogicMonitor Staff
  • Posts

    267
  • Joined

  • Last visited

Everything posted by Steve Francis

  1. The HTML widget now supports iframes, and allows you to do this (subject to the usual browser security limitations of mixed SSL content, cross origin, etc.)
  2. Yep. See http://www.logicmonitor.com/support/monitoring/networking-firewalls/netflow/
  3. Just install the Dell OpenManage Server Administrator package on your server. See http://www.logicmonitor.com/support/monitoring/server-operations-hardware/dell-hardware-health/ LogicMonitor will do the rest automatically.
  4. Yes it's possible, so long as each host is monitored by a different collector, and has a unique display name (to make clear what alerts, etc are referring to.) Note that you cannot add duplicate IPs using the Add Host wizard - you have to use the Add Device Expert mode.
  5. Only interfaces with a status of active are discovered for monitoring - but they are not removed when they go inactive, so they keep alerting. In this case, as the disconnected port is not active, just delete the interface instance in logicmonitor. That will remove the alert. If the port ever gets connected to something again, it will be re-discovered, and monitoring will resume.
  6. Collector grouping is out. Let us know if that doesn't address your needs...
  7. This is now fixed - if you set your company name under Settings...Account Information, it will be used in reports.
  8. Hopefully the new design brings you the best of both worlds, with the tree view and an isolation view...
  9. This was resolved quite a while ago.... Sorry for the late update.
  10. Connectwise integration is now 2-way. See http://www.logicmonitor.com/support/settings/integrations/connectwise-integration/
  11. Hopefully you've noted you've been able to do this for a while now....
  12. Good point. Not a way to do this currently - but as a (minor) help - the current version of ESX Datastore- datasource does not monitor latency - that is carved out to the ESXDatastore Performance datasource. (Due to the fact that the way the former queries data is not compatible with getting latency from NFS datastores.) So that will reduce the ineffeciencies a little, if you update to the current version.... We'll think about how to fix the other workflows.
  13. Hi David - we aren't currently working on an xMatters integration - it's on our list of things to do - just not at the top yet! That said, we can probably throw some pointers or help your way if you get stuck or have specific questions about the LogicMonitor integration functionality. Post comments here, and we'll see what we can do..
  14. See the section "Device or Group level filtering for event IDs" in http://www.logicmonitor.com/support/eventsources/types-of-events/windows-event-log-monitoring/
  15. By default, there are alerts if a device stops responding to WMI, or SNMP, etc. (And ping, obviously.) What kind of device was it?
  16. In the works (although it will be extended globbing - so /Data Center/!(*Servers*)
  17. From services, you can certainly post an XML request as part of the check. That is do-able now. Arbitrary ports are not available yet. Regarding devices - there is no mechanism for a collector to tell a remote host to issue a port check. You could fairly easily create a powershell datasource script (for windows) to do this, however. Something like https://social.technet.microsoft.com/Forums/windowsserver/en-US/7a3304c7-b564-4acc-ab28-2648a20f4bce/telnet-using-powershell?forum=winserverpowershell I'll add that our datasources dev queue - but you should be able to script it from there, if impatient.
  18. Good point and simple fix. We'll get that in the queue... Surprised it never occurred to us - or that no one else has suggested it!
  19. Thanks - I'll pass this on to the UX team. For UX feedback of this type, the best channel is the "Feedback" button in the footer of each page - but I'll pass this one on. Cheers!
  20. We do. What kind of devices are you finding this not happening on?
  21. THis is not currently possible, but this is on our roadmap - no scheduled time yet, though.
  22. There's no risk in reducing the number of files, or deleting past ones. They're only there for debugging. But - if you do have an issue, and it's a one time issue with the collector, it reduces the window you (or support) has to catch it in the log files, and you may have to wait for it to recur before they can identify it. But that's certainly not a common case....
  23. This is controlled by settings in wrapper.conf. e.g. wrapper.logfile.maxsize=64m # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=3 So by default there is one active file, and 3 "history" files. When the active file reaches 64M, files are rotated. Sometimes the max size and number of log files can be changed when people are debugging specific issues, but you can always set them back.