Widget for ping monitoring
Hi Everyone! I'm trying to figure out how to create a widget, that will show the top ten servers that have a ping of above 100ms. I can make the standard ping widget, but I don't see a way to limit the graph to those servers that have a high ping. Do I need to use the virtual datapoint? Or, maybe I need clarification on what it means when I select top 10 on an average, or maxrtt datapoint. Thanks!66Views1like6Comments
Dashboard graph widgets - aggregate by instance name / device group name
We have several clustered devices where metrics are gathered on each node. However, the instances across each node are identical. When attempting to graph this data, this means that I would need to add a new datapoint for each instance and use a glob pattern to select the devices from which to pull those instances. This can mean that a lot of time goes into creating these graphs if there are several instances to monitor. Examples: Three Solr nodes - each servicing search requests for the same 10 collections. In order to see the total number of GET requests for each of those collections, I would need to create a graph that has 10 individual datapoints. Instead, I would like to add one datapoint and have the graph intelligently aggregate all instances that have the same name, regardless of the node. Several device groups exist under a parent group. If I want to see the average CPU utilization across each of these groups on a single graph, I would need to add a separate datapoint for each group. A potential solution could be to allow the integration of regex instead of glob patterns to allow for capture groups. Otherwise a simple checkbox for "aggregate instances by device group" and "aggregate instances by instance names" when selecting aggregated graph types would be extremely useful and time-saving.21Views0likes0CommentsGauge widget multiple / virtual datapoints and datapoint as min / max
I was looking to create a dashboard gauge widget for memory used in a cluster. But to do this I need to have multiple datapoints and virtual datapoints (so that I can create a used memory expression using ActiveReal, TotalReal, and Cached) and also so that I could use the sum on TotalReal for the max of the gauge (so that it can automatically grow as my cluster does). I would expect this to work more similar to how the pie chart widget does now (allowing multiple datasources) but maybe only allowing 1 graph item.16Views0likes0CommentsServices on the Map Widget
It would be good to be able to combine device and service alert status on the same Google Map Widget. Use case: Offices are distributed around Europe, and a large number of retail stores (100+) are also being monitored using ICMP Services. By having both on the same map, it is possible to visualise the entire European operations.13Views0likes0CommentsDrill-down/Link-to items presented in Widgets
We use dashboards religiously in Logicmonitor - I'd argue they're one of LM's greatest features. When tracking issues or trying to ascertain trends among aggregate charts, drilling down to a single object is non-intuitive. For example, I have a line chart of CPU% for a collection of web servers. All follow a general path/trend, except for an outlier. I'd like to be able to jump straight from the chart demonstrating the outlier and drill down through whatever resources tree i might have. Today, I spend valuable time sifting through many objects to get to that data. My ideal scenario would take me straight to the single-instance version of that line chart for the requested host, making it a single click for me to navigate to other elements that I might suspect are the source of or related to the issue at hand. I hope that makes sense!12Views2likes0Comments
widget status via API
One of the most disappointing things encountered during a system review meeting with clients is to find widgets reporting "no data" because something changed or silently stopped producing results. In many other API endpoints, I have found there is a ton of state data embedded, but widgets have really nothing other than the lastUpdated* fields. I would like to see at least a field that indicates there is no data for some or all datapoints, just like you would see in the UI. Then we could generate reports on faulty widgets and be able to remain proactive. Thanks, Mark12Views0likes0CommentsDashboard widget exporting/importing
Hey guys, I just thought of something interesting that would be a nice to have. Rather than exporting the entire dashboard to xml it would be neat to export a widget.. The same with importing... when adding a new widget one of the options would be widget from xml. That way people could post sample/ templates of a single widget and others can manipulate the data / import it in to their dashboard. The thought came to me today as had just got done adding two graphs to a dashboard but am now export to xml to add 20+ datapoints to each graph.12Views0likes0CommentsChanges to the Big Number widget (more flexibility, this is a dashboard!)
A recent change to the Big Number widget has decreased formatting flexibility . It used to be that you could set thresholds to change colors if the number is between certain values and your "All other times" (else) condition could be any color you wanted to match the style of your dashboard. This allowed the flexibility to integrate the Big Number into your existing creative style with the added benefit of "POP" it falls below or between a certain lower threshold. For example, a red or orange number if server uptime is <=5 days, but grey or white text when that condition isn't met. After this recent change, anytime threshold isn't met the number is forced to be a "mild green" color which does NOT integrate well with most of the available Widget Appearance color schemas. Yes you can turn off thresholds and choose any number color you want, but you lose valuable attention-drawing functionality (which I would say is the point of this widget). In general, this really fouls up the asthetics of my client-facing dashboards. Have a look for yourself (attached). Please restore the flexibility (that we had previously) to change the Big Number "All other times" condition to something other than green. I'd suggest using the same color palat you get with the "Text" widget. This allows more visually flexible dashboarding and lets face it, dashboards are meant to be asthetically pleasing. Versatility of color goes a long way in achieving this. I've got a ticket open (99920) related to this suggestion, I encourage others to post comments (agree/disagree) here. Thanks everyone!12Views1like1Comment
