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 | LogicMonitor
Loginjestion based on event channels
In the support documentation https://www.logicmonitor.com/support/logs-partition#:~:text=Requirements%20for%20Creating%20Log,Resources%20Role%20Permissions. There it says "For example, you can keep high-volume application logs for just a few days if they are only needed for short-term troubleshooting. At the same time, you can retain critical logs—like Windows audit or compliance logs—for several months. This flexibility enables you to manage log storage more efficiently and predictably." What if you want to keep security logs in one partition and application and system log in another. This means you need to be able to assign event channels to log partitions to do this. Currently this can only be done on group or resource level with the "tenant.identifier" Please develop such a feature.Read-Only Non-SSO Access for Dashboard Wallboards
We use LogicMonitor dashboards on always-on screens in our offices (NOC / wallboard style) to show network and site health. The biggest issue we keep running into is that dashboards are locked behind SSO, which makes this use case really fragile. The screens run on domain-joined PCs, so when Windows updates or reboots happen, the SSO session expires, the page reloads, and the dashboard or playlist often stops. Then someone has to log back in and restart everything manually. For unattended displays, tying dashboards to an interactive SSO user just doesn’t work well. It would be hugely helpful if there were a way to expose specific dashboards in a secure, read-only way without a full login — something like token-based access, a service account, IP-restricted links, or explicitly enabled public URLs. That would let dashboards run continuously without breaking every time auth refreshes, while still keeping things locked down. Curious if others are dealing with the same thing.NOC Widgets - Support for LM Logs alerts
NOC Widgets currently do not support alerts from LM Logs. So if a device has an alert active for a log-based alert, it will NOT show as being in an alerting status according to the NOC Widget. It will still show as green. This is bad design in my opinion, NOC Widgets should show the alerting status for a device. Whether the alert is from datasources, LM Logs, or any other method should not make a difference. LM Support confirmed this is currently expected behavior, and a feature request would be required to fix NOC Widgets.LM Logs alerts and SDT
We recently found out that when we set SDT via email from a log-based alert configured in LM Logs, the SDT does not behave as expected. If we respond to an alert email to set SDT, it ends up getting applied to the entire log pipeline for that device. So if any other log-based alert triggers on that device from that pipeline, it will also be suppressed. That seems like a poor design choice. My request is that the SDT be applied to the specific log condition, not every log condition in the pipeline. This would be consistent with how datasource SDT works, where if we set SDT via email it applies SDT only to the alerting instance, instead of every instance of that datasource.Ingest collector events via LM Logs
I would like to request a method for us to ingest collector events via LM Logs. In the Settings > Collectors page we can see collector events from each collector. Currently there is no way to monitor the events however, they are only accessible from the Settings page. The events are not even accessible from the LM API. I think it would be useful to be able to ingest these events via LM Logs and associate them to the collector. This way we could detect anomalies in the collector events and alert on specific events which can indicate a problem.Aggregate Reporting by instance or property
I would like to request an enhancement to resource metric trend reporting. Could either be a new type of report or a new option on the existing resource metric trends report type. We have a use case where we need to report on what specific process is using the most CPU across a large group of servers. The best way to do this would be to sum up the CPU usage across all processes on all servers, then list the process name and their total CPU consumption over a defined time period. To meet that use case we currently have to run a regular resource metric trends report and then do some processing on the data in Excel to group by instance name and sum up the totals. My feature request is to allow us to report this way natively within LM. To allow us to report on metrics and group/aggregate the data by instance name or even a property name.
