Enforce Mandatory Audit Notes for LogicModule Edits
Summary: In a discussion initiated by Glenn Latour, a request was made to enforce mandatory audit notes for LogicModule edits in LogicMonitor. The current system mandates update notes for instance-level thresholds but allows optional notes for LogicModules, resulting in a broken audit trail and difficulty in troubleshooting. Glenn Latour suggests making the 'Commit Note' field mandatory with a character limit to improve administrative practices and auditing. Ryan Gillan agrees, noting that past changes often lack context due to missing notes. Sky Donnell acknowledged the request and forwarded it to the Product team for consideration.
Current Behaviour
When 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 Problem
Because 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 Solution
Make 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 Customers
Implementing 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.
Mike Moniz
·6 months agoI like the suggestion. I do want to note that many times our notes would just be a reference to a ticket number (which has all the details). So I would be careful about a minimum char limit. But I also don't see an issue with having someone having to put something like "see ticket #12345" instead of just "12345".
Sky Donnell
Admin6 months agoThank you for the detailed feature request, Glenn. I have shared this with the Product team and your account team so they can follow up on any updates.
Ryan Gillan
·6 months agoI know a lot of users who want this.
Nothing worse than reviewing a change made 6 months ago and zero comments why it was made.