Search the Community

Showing results for tags 'Column'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 3 results

  1. Mike Moniz

    "Column" type graph use

    Has anyone found any good use for graph's "Column" mode (vs line, area or stack)? Over most periods it either just merges into something that looks like Area, and over shorter periods it can look like lots of spikes. I can think of various items that would nice to report with a column/bar chart but only with the latest values of DataPoints. I'm not aware of a way to setup a graph to only show the latest values though and not over time.
  2. CBU BA DUDE

    New Columns in SLA Report

    The SLA report does not have an option to include information about SDT if the event is in the past. Since reports are often developed to look at sla information post-event it's imperative that report columns be added that reflect historical SDT info as well. I recommend not just including the sdted field to indicate whether or not the alert began in a SDT window, but to instead add a new field/column for % in SDT or SDT Duration that provides an indicator as to how much of that alert's period was happening in a SDT window. Example: Planned maintenance window is 2-4. IT change initiated at 2:30 and services are brought down. Alert generates and flags true for insdt and sdted (i think). If the change goes bad and services are still down at 4 AM the insdt flag is set to false (i think). The change implementer restores service at 4:30 and the alert clears. To report on downtime for that alert correctly we would need to know what portion of that downtime occurred within or outside of SDT. If we assumed that since the alert was generated in an SDT window (sdted=true) the entire duration was planned then we are incorrect an SLA report on downtime for that instance check would be false.
  3. 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.