Recent Discussions
Logsource property-based resource mapping
For script-based logsources it would be useful to have the option to map logs to resources by using custom log fields and matching them to a specific resource property. The logsource definition for script-based logsources already shows this as an option for resource mapping (LM Property Token). And the documentation lists it is as supported. However I was unable to get this to work, and was told by LM Support that it is not actually supported yet. My feature request is to add support for property-based resource mapping for script-based logsources. And also to remove it from the logsource definition and documentation until it is actually supported. Below is the link to the documentation where this is mentioned. Script Logs LogSource Configuration | LogicMonitorMSP Customer Branding
Would it be possible that when a user/group logs on branding for the GUI can be defined i.e. A customer logo assigned to the GUI rather than the global branding. I know this is probably not possible to the login landing page but afterwards it would be nice that each group or users can have seperate branding applied. Very useful for MSP's. I know of child tennats in LM but I believe this is not really supported any longer and may have cost implications (not sure)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.Dependent Alert Mapping - defining the originating alert
In the current Dependent Alert Mapping feature, alert suppression will only take place if an upstream device has an alert for the Ping or Host Status datasources for overall reachability. There are many cases where the upstream device will not be completely down, and instead will have an alert for an interface or BGP peer going down. This will still impact downstream devices, but Dependent Alert Mapping does not work correctly in these cases because the upstream device was not technically "down". I would like to request that the Dependent Alert Mapping feature give us the option to allow other types of alerts be considered when it determines what alert is "Originating" vs "Dependent". Ideally we would be able to define this when we are defining entry points. We could have the option of only using Ping or Host Status like the feature does today, or we could choose to select our own datasources for determining what the "Originating" alert is. This would allow us to get a lot more granular and make the feature a lot more flexible/powerful than it is today.
Dashboard Interlinking
Hi Team,<br><br> Is there a feature available to interlink dashboards? As per our requirement, when clicking on a device in the dashboard, it currently redirects to the resource tree info page. However, we need it to redirect to the graphs page instead.<br><br> If this isn't feasible, our alternative is to redirect to a new dashboard, passing the device name as a token.<br><br> Regards,<br> Sreekanth
Adding members (resources) as tokens to Services
Based on this page: https://www.logicmonitor.com/support/logicmodules/about-logicmodules/tokens-available-in-logicmodule-alert-messages We do not have a way of sending the members of a service as a token. This would allow us to include members into custom alerts and/or Intergrations This is handy to have as membership can re-evaluate after a time period.
