Search the Community

Showing results for tags 'dashboard'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • LogicModule Exchange
    • LM Exchange
    • LM Staff Contributions
  • Product Announcements
    • LogicMonitor Notices
  • LogicMonitor Product Q&A
    • Feature Requests
    • Ask the Community
    • From the Front

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Found 32 results

  1. Please make it possible to remove/hide the default Uptime widget from a device view. We have no use for this as we never use the uptime datasource so the widget always shows as zero and this is confusing for my users,
  2. A while back I published some very simple ConfigSources to monitor your collector .conf files: Here's an adaptation that writes the various collected configs to a dashboard, writing each of the config outputs to a text widget. Notes: THIS IS A PROOF OF CONCEPT. No warranty is given or implied (value of your investments may go down as well as up, check with your health professional before taking this medicine, etc). Please test before deploying! As with all data within LogicMonitor (or any system), be aware of access rights of users - in this case to whatever Dashboard(s) the config data will be presented on. Be sure to configure your Roles and Users such that only users who have legitimate need to see this data can access whatever Dashboard(s) you send it to. This uses the REST API v1 to verify the target dashboard exists or create it if it doesn't, and also to create / update the text widgets. It will therefore need an API token for an account with management permission for the relevant Dashboard(s), with ID and Key values set as device properties apiaccessid.key and apiaccesskey.key. All of the API interaction is contained with a groovy checkpoint, rather than within the config collection script, so this could very simply be copied into other ConfigSources. The same logic could be used in other LogicModules, such as to write non-numeric outputs of SQL queries or any data collection methods to dashboards. While this provides no history retention as written, it will show current / most recent values. Within the script you can define the desired Dashboard path, e.g. 'Collector Configs/Groovy Check' (default as presented here), Dashboard name (hostDisplayName is the default), widget name format (hostDisplayName: wildvalue) and other initial parameters such as widget colour scheme, description, etc. This is written for REST API v1. One day I may get around to updating it for v2, for greater efficiency, but today is not that day. Tomorrow is not looking likely either. Dashboard text widgets do have a maximum character limit (65,535 characters). I don't think I've seen a collector config near to or in excess of this, so I have no idea whether a larger config from another device would be truncated or whether the widget creation would fail. Other widgets on the dashboard are unaffected by this script creating and updating widgets; likewise later manual changes to widget size, colours, etc should be respected; updates should be to the text content of the widgets only, so the target dashboard could contain other data from the device. For example, it might look a bit like this: Known issues: On the first config collection for a multi-instance ConfigSource like this, and where the target dashboard does not already exist, only one widget will be created in the dashboard. This is because all instances collect more or less simultaneously, and each determines the dashboard is not initially present. Each, therefore, attempts to create the dashboard and as soon as the first instance does so, the others will fail as they cannot create a dashboard that (now) already exists. This could be coded around with a simple delay / re-check on failure, but I haven't had time, and the second config collection will create all expected widgets without issue. Additionally, if you create the dashboard first, this issue will not occur.
  3. Please add the ability to set a dashboard as the global default for all users so that when any user clicks the "Dash" menu option, they are taken to the default dashboard that the administrator sets. We have a dashboard that we use as the landing page with HTML widgets, it acts as an index to other dashboards. We want all users to be taken to this landing dashboard when they click the Dash menu option. Thanks.
  4. Michael Lorincz

    Fetching A Specific Dashboard URL

    Hello all, I am currently researching the possibility of running an integration between ServiceNow, an application my company utilizes, and LogicMonitor. I have a request from an end user to open a specific dashboard (this dashboard is different depending on certain conditions, but it is the same type of dashboard) when a link is clicked on the ServiceNow side. After looking at the REST API for LogicMonitor, specifically the API for getting information about a dashboard, I haven't found anything that points to the ability to grab the dashboard URL. I am able to craft a hyperlink such that it opens to ALL the dashboards for my company, but since the dashboards don't seem to follow a set pattern in their URL end-tags, I haven't been able to find a way to make the link dynamically specific to the dashboard that the end user wants. For reference, the desired dashboard URL will resolve to, I need to know how to get either the entire URL or the dashboard number at the end (which is DYNAMIC), if possible. Any input you may be able to offer is appreciated. Thank you for your time!
  5. 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.
  6. Jeffrey McGovern

    Dashboard Group Cloning

    Looking for a simpler way to create standardized dashboards during onboarding process. Use case: I am an MSP who builds three (three is arbitrary but this story gets worse if this number grows) default dashboards for any customer who signs up for my service. As an initial step the provider creates these dashboards using widget tokens and place them in a non-customer facing group so that the provider onboarding operators can clone them. Today this means that the operator must: 1. Go into the dashboard section of the UI 2. Create a new dashboard group for the new customer, 3. Clone dashboard 1, update the group, and then update widget tokens for dashboard 1 4. Clone dashboard 2, update the group, and then update widget tokens for dashboard 2 5. Clone dashboard 3, update the group, and then update widget tokens for dashboard 3 6. Wash, rinse, repeat Request: UI: Move widget token metadata definition to the group level as an option and then allow dashboard cloning at the group level. This changes the process above to look like below regardless of how many dashboards exist. 1. Go into the dashboard section of the UI 2. Create a new group 3. Clone the dashboard group, change the widget token, change the group, and then go about their business. API: This process would then simplify the onboarding code dramatically as there would be no need to iterate through the existing group to gather data before the code could continue with the cloning process.
  7. Hello LM Team, It would be great if the NOC widget in the Dashboards have the possibility to filter out inactive devices and show only the ones that actually have alerting enabled. For example we have VCenter that have 1500 virtual machines, but only about 10% of them are to be monitored at all times, so by default alerting is disabled for all VM machines from VCenter but these we actually need. Unfortunately the NOC widget will show us everything from that Datasource and it's problematic. Thank you.
  8. mkerfoot

    SLA Widget

    I believe that we have found a bug, right now if more than one service monitor is set under the SLA Monitor Widget the results seems to be the average. example; graph 1 = 100 % uptime graph 2 = 50% uptime Combined SLA widget(graph 1 and 2) = LogicMonitor is returning 75% where I would expect to it return the lowest uptime percentage which would be 50%.
  9. Hello, We would like to see you add a weather layer to the maps widget. The main reason for the request is to see if any weather systems could be impacting our customers remote sites. 1. If a circuit is down, could it be due to weather in the area? This will help us better react and provide customers direction when dealing with carriers. 2. Monitor popular DC/COLO areas of the US, are there any weather systems in the area which could be impacting service? Thanks, Mitch
  10. Currently table widget lists 'all or nothing' data. It would be useful if we could filter out eg. "show only if value is X or more/less" etc..
  11. Stephen Voorhees

    Maximum Number of Dashboards in Slideshow

    Hello all, This is my first time posting a question in the forums. I wanted to know if there is a limit to the number of Dashboards that can be added to a Slideshow dashboard rotation? I work in my company's NOC (network operations center) and have somewhere in the neighborhood of 70 dashboards that my group needs to keep track of. It seems the number of dashboards I can add before a previously added dashboard is removed is 26. Does anyone know if this is a hard limit or is this a setting that our LM administrators can adjust? Looking forward to responses, Steve V.
  12. We'd like the ability to illustrate a data center "rack" physically on a dashboard. In simplest terms we'd like to be able to custom sort and arrange items in a single column NOC Widget to represent hardware in a rack. The current sorting options on this Widget don't allow this (alphabetical or alert severity). Ideally we'd really like a new "Rack" widget into which I can drop in devices in the appropriate "U" locations giving an instant rack health overview capability on a dashboard. Longer term LM could take this further and have a free-form dashboard Widget/container onto which users can drop networking devices and "connectors" to mock up an indicative network schema. The above ideas would give users visibility of rack and network health in a more meaningful and intuitive notation.
  13. I would really like to see a feature implemented that allows for easy and adjustable graph smoothing. This can be accomplished by adding a switch to the UI in the graph configuration screen. If the switch is turned to "enabled", a drop-down appears prompting for an integer between 1% and 5%. This number would represent the percentage of total datapoints that would be used to calculate the "smoothed" values. A second drop-down prompts for the position of the calculation: past, future, or both (default). For example: A graph containing 500 values - Rolling average is enabled and set to 3% (both). Each value on the graph would be recalculated to reflect the average of itself, plus the 15 (3% of 500) preceeding and proceeding datapoints. Here's what the original data might look like: (All examples below were created with TimeLion in Kibana using a similar algorithm) With 3% smoothing: And with 5% smoothing:
  14. Hi, i am planninf to play our internal custom vedio clip in dashboard (dashboard playing on wall TV). I know some options to play youtube vedio, but how to play internal vedio link ?
  15. I'd like to see the ability to utilize the already available variables for emails, data, etc in the dashboard widgets. For a lot of JMX monitoring we use Regex to group the JMX #'s to define which unique service they are supporting. For some JMX beans they use random identifiers below the jmx port such as JDBC connections. We'd like to see the ability to tag the data on the graphs with ##INSTANCEGROUP##, etc to help better display the data.
  16. I'd like to see the ability to utilize the already available variables for emails, data, etc in the dashboard widgets. For a lot of JMX monitoring we use Regex to group the JMX #'s to define which unique service they are supporting. For some JMX beans they use random identifiers below the jmx port such as JDBC connections. We'd like to see the ability to tag the data on the graphs with ##INSTANCEGROUP##, etc to help better display the data.
  17. It would be great to be able to build dashboards with widgets associated with devices that the users role doesn't have access to. We have several "teams" at our organization that support several applications that have dependencies on large storage filers. I would like the ability to add a NetApp Volume Usage graph to their dashboards for only the volumes they are interested in without having to give them view rights to the entire NetApp filer. I ran into this limitation today when building a dashboard for a group only to find they couldn't see the graphs because they didn't have view rights to the group that the NetApp filer resided in.
  18. When Configuring Dashboards there are relatively few predefined Time Ranges that you can choose. There is an option to create custom time ranges, but when you create a custom time range it is static. The predefined time ranges are all relative to the current time. Request 1: Allow administrators to modify (add/remove/edit) predefined "Relative" time ranges Request 2: If for some reason Request 1 poses significant obstacles, can you add predefined time ranges for "last 8 hours" and "last 12 hours"
  19. Has anybody encountered the fact the that "Peak Time Range" selected will not persist anything other than the "Last 30 Days" selection. I've tried a bunch of things to try and figure it out. I can see that the request shows "Last 30 Days" regardless of the drop-down selection.
  20. Hi, The custom graph could do with being a bit more customisable. Presently the X-axis is alway time. This is often useful but not always. It would be great to be able to define what's on the X-axis either just in terms of values or from datapoints. This was found whilst trying to create a dashboard to show disk space usage in a visually meaningful way. Thanks Mike
  21. 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.
  22. Jake Schmidt

    Weekday Reports

    Hello, I'm looking to have an option to send dashboard reports only on weekdays. Less clutter for emails I don't need/read on the weekend. Thanks! Jake
  23. Willing to create a single dashboard which would show the utilisation of multiple routers. The widgets for each router shall be grouped under the routers host name as a group The widgets could be CPU , memory, status like up/down/shutdown and so on
  24. It would be very cool if you could toggle and make visible the historical alert types that where triggered by differentiating the graph backgrounds. See illustration
  25. Dashboards are a fantastic feature, but the way the widgets and data source graphs snap is a huge inconvenience. Everything shifts up/down, nothing shifts left/right. If I make a grid of widgets that runs left-to-right (say each row is a server), it makes adding a new server to the bottom very simple. It (however) makes adding a new metric column a HUGE pain in the butt. If I want to add a new column to the left (for each server - like a new metric), I have to move EVERY.SINGLE.GRAPH in the whole dashboard to make it all line up... I think a FAR better approach would be to have the dashboard grid simulate the face of a smartphone. If I move a widget above another, it should shift down (like it does). If I move it to the left, it should shift right, not down! This would make designing an organized dashboard SO much easier (I've literally spent hours just adding a single metric across all our dashboards because of this stunting behavior). P.S. - also consider giving the ability to bucketize groups of graphs. Giving me a colored backdrop to put behind all my CPU metrics or all of my metrics regarding ServerX would be a nice visual aesthetic.