Enforce Mandatory Audit Notes for LogicModule Edits | Feature Requests

Glenn Latour · 2026-03-31T00:50:46.414437Z

Current BehaviourWhen updating a threshold at the instance level, LogicMonitor correctly enforces a mandatory update note before allowing the user to save. Conversely, when modifying a LogicModule (such as a DataSource or PropertySource), the commit note is entirely optional.The ProblemBecause the module update note is optional, engineers frequently bypass it to save time. This breaks the audit trail. When troubleshooting broken monitoring or auditing historical configuration drift, it is exceptionally difficult to determine why a core module was altered without hunting down the original author. Furthermore, even when users do leave notes, they are often unhelpful single-character entries just to bypass internal team policies.Proposed SolutionMake the 'Commit Note' field structurally mandatory whenever a LogicModule is saved, updated, or committed.Introduce a minimum character limit (e.g., 15 to 20 characters) for this field. This will prevent users from submitting meaningless strings (like "x", "test", or "updated") and force them to briefly articulate the actual change.Value to CustomersImplementing this feature will align LogicModule management with the existing, robust governance already applied to instance-level thresholds. It will guarantee a reliable audit trail, significantly reduce troubleshooting time during monitoring outages, and enforce proper administrative hygiene across shared engineering teams.

MoreDiscussions

Enforce Mandatory Audit Notes for LogicModule Edits | Feature Requests | LogicMonitor Community