No Referential Intergrity when renaming or moving host groups

On 6/9/2014 at 5:00 PM, John Dear said:

 

When I rename or move a host group, any resources that has references to this revised group path will most likely become non-functional. Resources include dashboard widgets, datasources, reports, alert rules, etc. There appears to be no referential integrity automatically maintained by Lomo at least in this area. There is no resources cross-reference report to assist in identifying referencing resources that requires modifications, so I have to search everything manually. I have to do this every time I make a change to a group name or move a host group. Looking for better way.

I've run into the same issues.  At a minimum, I've asked LM to inform the operator that the rename may have impacts to Alerting, Groups, Dashboard Widgets, etc. I'm not sure (especially with globs) if LM can "auto-correct" these mappings on a rename, so just informing the operator for me is a great start.

We have also run into this issue. A group was accidentally moved and any datasource that was being applied based on that group no longer worked and data was lost. A work around we used was to edit the datasource to be applied based on a system category added to these groups rather than actual group.

I'd still like to see LM be able to track when a group is moved and edit any resources referring to that group. As it is now it is a pain to fix dashboards and reports once a group has moved.

Unfortunately this applies to everything I've seen within LogicMonitor. I renamed an Integration right before leaving last night, hoping for an entire evenings worth of data to look at, only to find that the Integration didn't get invoked. The Integration references in Escalation Chains also needed to be updated too.