Is anyone else getting issues creating Bandwidth Reports on Switches?
Currently attempting to generate a Bandwidth Report with more than 10 interfaces causes an error, where previously it would just create a report and provide the “Top 10” interfaces. I am curious if anyone else is having the trouble. Also, Netflow reports generate the same error, logs indicate an inability to create more than 20 graphs. This error is odd, as just a few days ago we had a report run with over 30 graphs without issue. Curious if anyone else has run into this issue.Solved257Views2likes8CommentsGetting Graph Sharing Token via REST API
Hello, I am new member of LogicMonior. I have created new dashboard and done about adding device graph into dashboard via API, it work! but now, I want to generate “Widget Embedded URL” and also get “Sharing Token” via REST API, after created graph on Dashboard. Is it possible to do that? Thank you very much for all recommendation and commentSolved218Views24likes14CommentsGraphs Device View vs Ovewview default?
As a portal admin on my site, I admit I very infrequently look at graphs tabs, I’m normally digging about in raw data or alert rules or datasource definitions etc. It was brought to my attention that a Customer is unhappy that when they go to their graphs tab, they get some device view by default, and not the overview. They hate having to switch it. When did this start? I guess I should read the release notes closer. Is there a way to change it back? Or are we stuck with the “Device” view being default?Solved133Views11likes4CommentsGetting specific datapoints using the REST API
In this post: https://community.logicmonitor.com/archive-13/getting-datapoint-data-via-rest-api-1249 … @Sarah Terry provides information on how to get data for just specific datapoints, reducing load on the API, minimizing network traffic and reducing deserialization load on the client. While this is VERY useful, it is not currently possible to do this for graph data. An example of such a call would be: {{logicmonitor_url}}/device/devicedatasourceinstances/229505122/graphs/-1/data?datapoints=sentpkts … which brings back the default graph data (all datapoints), though this would also work for a specific graph. The advantage of this approach to data fetch is that it permits the retrieval of virtual datapoints. In order to achieve the same benefits, we (Panoramic Data) request that the same datapoint filtering is added to the {{logicmonitor_url}}/device/devicedatasourceinstances/{instanceId}/graphs/{graphId}/data endpoint. Of lesser importance would be other graph API endpoints (e.g. the website graph API endpoint) Thanks in advance! David53Views15likes0CommentsConfigurable stroke widths for graphs
In the graph configuration page, please dd option to set set the stroke width for line graphs. The current fixed stroke value is too thin when displaying graphs on big screens and viewing them from a distance. Ideally this this be an input value so we can set any value we want, but if these need to be predefined options, then 1px to 10px at least.11Views0likes0CommentsEnhanced Reports with Graphs and Alert Trending
As we have implemented LogicMonitor we have worked to stabilize and tune alerts as well as to remediate real problems identified by alerts. To track this progress we wanted to graph the alerts overtime. We sort the alerts into several categories such as severity, group, device. To do this we have to create a detailed report, pull the data into Excel and create pivot tables and pivot charts. Create alert trend charts in LogicMonitor reports, directly, would be a valuable tool for teams working to drive down the alert counts. Attached is a simple graph we have created multiple times in Excel as an example. We have others. Thanks. Todd Kelley10Views0likes4CommentsDisplay more details on graph datapoints
Many of the graph points in LogicMonitor hold descriptions of what the data supports. IE: for status 1=OK, 2=Down. Some of these are very long descriptions and when users are mousing over the graph they can only see a bit of this information. In order form to know what all the options are, they have to dig into datasources to figure out what is being reported. I suggest to either expand the data to show everything when you mouse over the datapoint, or allow a function of the graph to extend the side and print the description off the side of the graph if the user wants to see. This can be used in so many ways and is much more user friendly then having a user dig into the bowels of the tool to find what a number like 8 means when collected.7Views1like0CommentsAllow Logarithmic scaling of graphs
It would be great if graphs could auto-scale using a logarithmic function so as to display data that tends to have wide variances. Currently, if one instance has an extremely high value, all other instances in the graph appear at the very bottom. A checkbox on the custom graph page should allow the graph to scale appropriately so as to keep that data visible.6Views0likes4Comments