Show "Bottom 10"
Currently the graph options for Widget includes three was to "Limit Results". The are "Top 10", Aggregate, All. There are times when I want to display the "Bottom 10". For example the lowest 10 CPU devices, or the 10 least available devices, etc. It would be GREAT to have a Bottom 10" option in the Limit Results parameter. Thanks.32Views4likes11Comments
Dynamic Tables (dashboard widget)
Currently, a table must have static columns and rows defined before the widget will display data. It would be great to be able to dynamically build a table's rows based on * To expand on this, it would be great for the table to have the option to exclude instances with zero/no data from the list. For example, I would like a table that displays all MSMQ queue names and the number of messages in each queue - but not display anything if the current queue length = 053Views3likes13CommentsSpeedtest Option
It would be nice if we had a way to invoke a speedtest and record the data pulled down. This could easily be done using a powershell script and a datasource but I'm still fairly new to logicmonitor so creating a data source isn't really something I'm good or comfortable with.82Views2likes16Comments
SSL Cert expiration alerting
Some other monitoring tools provide SSL certificate monitoring to alert for expiring certs. Really wish LogicMonitor had this. +1 if I could use a collector to monitor for private SSL certs that aren't accessible publicly (like for RDS and the like).134Views2likes12CommentsVMware - vCenter view of VMs - what host they are on
Within the interface there is a nice long view of VMs when you are looking at a vCenter system and are within the Virtual Machines datasource. I assume the data is gathered already but it would be awesome if there was a dynamic update for the VM to know what host it is on as part of the display of that datasource. Instead of: dns01.dufus.devdns02.dufus.devdns01.dufus.proddns02.dufus.prod How about: dns01.dufus.dev (host01.cluster01.lcl)dns02.dufus.dev (host02.cluster01.lcl)dns01.dufus.prod (host01.cluster01.lcl)dns02.dufus.prod (host03.cluster01.lcl) This would make further diagnosis easier as you jump around from vCenter to a host. When clusters are 8-20 hosts in size it can take a while to figure out where that guest lives and this would shorten that time quite a bit.20Views2likes6Comments