Search the Community

Showing results for tags 'Alerting'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 11 results

  1. Hello, I was wondering if there was a possibility to impose a duration constraint on a threshold in LogicMonitor... I see where you can enable dynamic alters but was not sure if they would look back to the duration of the alert rather than just a floating data point that it would attempt to normalize. Thanks in Advance
  2. When there is a legitimate reason for disabling alerts for a device, it would be very useful to be able to leave a note as to why (and by whom). This would prevent confusion with teams, where the case of "why would this be disabled" would come up frequently. For example, there is a known bug with a certain version combination of ESXi and HPE servers that triggers a false-positive hardware alert internally, so we disable alerts for that instance on servers that meet the criteria as we encounter them. Or, some QNAPs will give false-positive alerts that their disk is full when in fact it is
  3. It would be immensely helpful if I could see and test alert routing from the Cluster Alerts page at the device group level similar to the existing Alert Routing button on the Alert Tuning tab. As we begin to more heavily utilize this functionality, it's critical that we can verify that alerts are routed correctly wherever we set it up.
  4. It would be great to create alerts from multiple data-points from multiple data-sources. For example if CPU is above 30% and SQL database lock timeouts is above 1000. I can see many uses cases to be able to alert on different datapoints that relate to other datapoints in other data-sources.
  5. I see a need in the design to alert on deviation from rolling average: example 1: Temperature in hardware is based on fixed baseline (default or manual adjusted) or based on fixed Delta. In real world application it would Make a LOT more sense to alert on Deviation from a 5 day or 30 day rolling average Temp of the box. Reason is, units alarm on the weekends because the office shuts off the AC during the summer. or they alert During the week 9-5 because in the winter the offices crank the heat. All of these ignore nuance of RANGE and Average expectation for the locatio
  6. Hey LM team, There are a number of options to customize what is in a service alert as well as a data source alert, but config source? Nope, can't modify what gets sent. All it says is that a change was made and gives you a link to the device. A couple things I think would be beneficial as a new feature, 1. Being able to put what lines were added or removed right in the alert. For simple configs you can then tell right away if you need to take action or not. 2. Have the link in the alert actually bring you to the diff view of the current and last config state. While having to c
  7. We think there needs to be another level of privileges between Acknowledge and Manage. We would like to be able to give our operators the ability to toggle the Alerting On/Off slider option without giving them Manage rights. Also, we'd like to give them the ability to perform Poll Now without giving them Manage rights.
  8. With DataSources and EventSources it is possible to tailor the alert message and content of the alert emails. However, with web services there is only the one template. We need to be able to tailor the email content on a web service by web service basis. Please make it possible to configure the alert email content per service check. Ideally it should be possible to define as many message templates as we like, and then choose which template to apply at a service group level, so that the service check objects inherit the template from the parent service group.
  9. It would be good to be able to set AlertRules based on DataSourceInstanceGroups and DataSourceInstanceProperties
  10. We completed a new integration and after a lot of effort we discovered that the escalation "NEXT" performed the create but subsequently every n minutes a new ticket was created - the ACK also still needs to be performed. Ideally, we would want the escalation to create the ticket and acknowledge the alert. Perhaps the escalation then has a null destination until it clears (active alert) or some other method to avoid repetitive case creation? I had a thread with Desh on support - no suggestions on a workaround.
  11. I would love it if we could reference ##SERVICESRESPONSE## on an overall alert. We don't deliver alerts for singular test location failures, since our mandate to only notify on systemic issues across all test locations. So the question will probably, which response to include in the event there are differing responses? Why not include all of them! Or only include the first one in the test location array for that service. Or pick a random one. Or arbitrarily decide certain failure reasons have a "higher" priority than others and choose the "highest" one.