Search the Community

Showing results for tags 'availability report'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • From LogicMonitor
    • Product Announcements
    • LM Staff Contributions
    • Community Events
  • LogicMonitor Product Discussion
    • Feature Requests
    • LM Exchange
    • Ask the Community

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 1 result

  1. 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.