Best Practices for removing clients from LogicMonitor

Remember to back everything up first. If you don’t yet backup your LogicMonitor portal(s), DM me.

You should remove client-related items in the following order.  Like provisioning, you should script this, as it’s a pain to do it all manually:

• LogicModule Group (if you have any customer-specific LogicModules)
• Integrations (these can’t be grouped)
• Alert Rules (these can’t be grouped)
• Escalation Chains (these can’t be grouped)
• Recipient Groups (these can’t be grouped)
• User Group
• Role Group
• Netscan Group
• Website Group
• Service Group
• Resource Group (remembering to HARD delete Resources by removing them from recently deleted if you are using the UI)
• Report Group
• Dashboard Group
• Open Telemetry Collectors
• Collector Groups

Of course, there should be ONE GROUP PER CUSTOMER and should be tagged with the customer code. We use a simple 3-letter all-caps code like “ABC”), but you will probably have a different system. For example, our Report Groups will be named consistently for all group types:

• “ABC - ACME Broadcasting Company”

Where entities can’t be grouped (like Integrations), we make sure that they start with the three-letter customer code.