Alert Rules Priority Value Duplicates
Is it acceptable for alert rules to have the same priority value if they differ in other properties, such as Group, LogicModule, Instance, or Datapoint? Additionally, can I increase the default alert rule limit from 100 to 1000? If so, will this change affect any alerts that have already been triggered?61Views4likes3CommentsCustomer Story - Banking
Customer Story: This US credit union is the largest community-owned financial institution in the US Northwest, offering mortgage loans, savings accounts, auto loans, and more. Industry:Banking Challenge The IT team needed to mitigate “911 events” within their infrastructure. With minimal visibility, each of these events caused the entire team to drop everything to investigate the issue, leading to inefficient work and valuable time spent troubleshooting instead of larger projects. Solution Simple, high-level executive dashboards displayed critical information about the health of the environment, with the ability to drill down on a specific issue. Alert rules and escalation chains improved alert routing to select teams for quick resolution. Business Outcomes 90% reduction in alert noise within 6 months More time spent on innovative projects instead of troubleshooting Improved visibility into network health across the organization Interested in sharing a story about your infrastructure monitoring, processes improvements, or any other successes since implementing LogicMonitor? We’d love to hear it! Feel free to comment below or reach out to us atinnercircle@logicmonitor.comto share your voice.80Views22likes0CommentsIs there a way to configure an Alert Rule to only match websites OR resources?
If I have a group under Resources called Production, and I have a group under Websites called Production, because LM only matches things based on Text, there doesn’t seem to be any way to specify which of those I want to match. This also means that if I ever rename a group, I will break the alert rule since the text will no longer match, but that’s a different issue. I wanted to make a catch-all group for resources and one for websites, for anything that isn’t being picked up by an alert rule. But I want them to go to different places which doesn’t seem like it’s possible, unless I’m overlooking something. Thanks.Solved127Views19likes3CommentsAlert Rule Syntax
Hi, Because LM uses Text-based matching, I know it’s picky about how you configure alert rules with regards to /s and *s in the Group field. I just want to make sure I understand this right. I pulled a list of every alert we’ve gotten for the last year, and compared that to our list of Alert Rules, and found some problems. I noticed we have some things setup incorrectly in our portal and we might be missing alerts. Scenario: Let’s say I have a group called Production Servers. Inside that group I have groups for Web Servers, App Servers, and Database Servers. Let’s also say each of those sub groups have other sub-groups inside of them. Each of the groups has servers in them. If I have an alert rule set with group “Production Servers”, will that find servers that are in the Production Servers group but not in the sub groups? If I have an alert rule set with group “Production Servers*”, will that find servers that are in the Production Servers group AND in any of the sub groups? If I have an alert rule set with group “Production Servers/*”, will that only find servers that are in the sub groups, but not servers that are in Production Servers? Are there any other variations on that I should keep in mind? Thanks!71Views5likes3CommentsCan we get the ability to better control alerts rules (not limited to cloning)?
The ability to clone an alert rule would be fantastic, but being able to create an escalation chain from within an alert rule, so you don’t have to go back and forth, would be fantastic. Can’t tell you how many times I’ve created a rule and get down to the bottom and realize I forgot to make the chain first. It’s incredibly annoying (though I do know i can just save, create the chain, and come back and edit, but I’d like to just be able to do it all on one popup).37Views17likes1CommentAllow Multiple LogicModule Selection for Alert Rules
My organization originally committed to only creating tickets for CRITICAL level alerts, but naturally marching orders came down to create ticketsat WARNING with vastly different set of ticket parameters. The kicker--do this only for specific LogicModules. I figured this was easy enough, until I saw that I wasn't able to select multiple LogicModules for any given alert rule. These LogicModules varied names and datapoints. Creating a glob expression that is not going to cause someone to go cross-eyed would be herculean feat. So instead of adding multiple alert rules with the same set of parameters--level, escalation chain, device/website groups--save LogicModule, please add the ability to configure alert rules to accept multiple configured LogicModules.27Views0likes3CommentsCluster Alert Routing
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 existingAlert 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.4Views1like0CommentsMake Instance Groups searchable/filterable
Hello, We'd like to request some more usage for instance groups. Right now, it's just not very useful to group instances on a datasource. We have shared devices with datasources belonging to different teams and we have to create dashboards and alarm rules regarding those. Right now, we have to use the wildcard filter in a "creative" way to have shared devicealerts and dashboards from different teams configured. It would be really helpful if the instance-group namecould be used in Filters. Use-Case: * To configure alert rules for shared devices for different teams, we can group all datasource-instances in instance groups named "teamname" and then filter on "teamname", this works even when we use "*" for device/devicegroup, as long as instancegroup "teamname" is persistent over multiple shared devices. * To have dashboards for shared devices on a per-team base, we can filter for the teamname when creating those dashboards. This also works with "*" as device/devicegroup query, so instances on new devices will be added automatically. Regards, Bastian8Views3likes2Comments