Recent Discussions
Azure Automation Account Runbook job status
We are trying to monitor the Runbook status of different Azure Automation Accounts. For example we would like to receive any alerts, when a job status is "Failed" instead of "completed". With the current Azure Automation Account module there are only metrics for the job count and nothing about the status of the job itself.
Dependent Alert Mapping - reviewing cleared alerts
I recently had an LM support ticket open for some confusion we had around the Dependent Alert Mapping feature. Wanted to document some areas for improvement here that would make the feature work better. Currently, when an alert clears which was processed by Dependent Alert Mapping, the "Routing State" and "Dependency Role" columns set to blank. This makes it challenging to go back and review alerts after an outage to see what was "Originating" vs "Dependent" Please update the feature so that these columns on the alert table are still populated after an alert clears. This will help us with reviewing and reporting on resolved outages Currently when an alert is suppressed by dependent alert mapping, the alert message contains a lot of useful metadata related to the alert suppression. But if the originating alert clears and the dependent alert is still active, all of that metadata is removed and there is no indication that the alert was ever suppressed by the Dependent Alert Mapping feature This causes confusion when we go back to review past outages. It makes it look like the feature did not work as intended, even if it did. Fixing this along with item #1 would make the feature a lot easier for us to use and understand what it is doing.
Feature Request: Alerts Clear Customization
It would be a great feature to allow customization when alerts clear in the Manage Alert Rules. Currently its off or on. Currently our escalation chain includes a phone call for Critical alerts as well as an integration with our ticketing system on Stage 1. When that alert clears, we still want the clear alert to go to our integration, but we don't want to trigger a phone call.dashboard display user timeout override
We have several ( hundreds of ) dashboards which show pertinent data to the relevant teams here. Each set of teams sit in separate areas, and they all need to see their dashboards. As such, we have set up dashboard stations ( computers with a bunch of screens attached ) so they can put all their dashboards in their own areas on a specific wall etc.. The only portal which is timing out is the LogicMonitor portal. Is there any way to override a specific account to not be bound by the portal settings for idle logons? We need to keep our. timeout settings as 4 hrs for all other users, but these specific screens need to remain forever not being logged out ( as much as is possible ) Is it possible to have a per-account override for “user session timeout” ?Synthetic Datasources - Complex datapoints
I would like to request that we have the option to create complex datapoints for the below 2 datasources. These modules currently cannot be customized without breaking, which LM support confirms is intended behavior for the synthetic datasources. Selenium_Synthetics_Overall SyntheticsSelenium I have a need to stop alerting on a specific status code (430 - Session not Created) which can only be done using a complex datapoint. This status code is reported when there is an issue with the Selenium node itself, not with the synthetic check necessarily. So when the Selenium node has an issue, we get a false alert from every synthetic check assigned to the Selenium node. We want to have alerts for a status code of 430 alert via a separate datapoint so we can route them to the team who manages the Selenium node. Instead of having them all be routed to the owner of the application we are monitoring with the synthetic check, which to them is a false alert.Network Interface - interface.description.alert_enable Property
Request that when the 'interface.description.alert_enable' property is used to identify interfaces we want to monitor and alert for UP\DOWN, that the 'Alerting Status' toggle, in the 'Instances' view within the UI, changes to OFF in the LogicMonitor UI for those we don't want to alert on. As opposed to having to manual check and review the RAW DATA for each interface and verify that the status is either '1' for alerting enabled or -1 to indicate alerting has been disabled.
Scale Computing HyperCore modules
With more and more customers looking to switch from VMware to Scale Computing HyperCore due to increased licence costs, it would be good if there were modules directly setup to cover collecting metrics e.g. Datasource, ConfigSource, PropertySource etc I'm sure the industry is going to be moving at large scale from VMware to Scale Computing HyperCore so it would be good to get this on the LogicMonitor radar. ThanksUIv4 Issue: Alert links no longer open new tab
I noticed that in UIv4, several types of alert links no longer open a new tab when you click on them. Instead they open the link in the current tab. This makes it frustrating to drill down into alerts when looking at a dashboard or list of alerts on the Resources tab. The below types of alert links no longer open a new tab, where they always have prior to UIv4. This negatively affects our NOC's workflow of troubleshooting alerts during an outage. Alerts tab on the resource tree when clicking the Resource or Instance links of an individual alert Alerts widget on dashboards when clicking the Resource link of an alert this used to go to the alerting instance Resource or Group link on log entry in LM Logs page If I am looking at a list of filtered alerts on a folder of the resources page and then click one of the alerts, I then would have to hit the Back button on the browser to go back to the folder and would lose filters. Same if I was looking at dashboard alerts, if I drill down into one I then have to press Back to return to the dashboard unless I do right-click and "Open New Tab".Add “Low” and “Informational” Severity Levels to Alignment with ITIL Framework
In an MSP environment, it's important to align the monitoring system severity levels with that of the ticketing system. Please consider adding the following severity levels: Low – For alerts that indicate minor issues or early signs of potential degradation, which do not yet require immediate action. Informational – For non-actionable alerts such as status updates, successful job completions, or environmental observations.