Hello,
We are glad to extend support for setting up configuration profiles and third party integrations at the MSP account level.
For now, only threshold, notification, location profiles, and email templates; and third party services including Webhooks, PagerDuty, Slack, OpsGenie, and ServiceNow can be configured at the MSP account level.
Some important points to note:
- When a new configuration profile is added/an existing profile is updated, it will take some time for the sync to customer accounts to complete successfully. In case of any failure to update, an email would be sent to the user who performed this action.
- For notification profiles, Escalation Settings is not supported at the MSP account level. You can configure these settings for each of your customer accounts individually. These settings will not be overwritten during profile sync.
- While setting up third party integration(s), although the All Monitors option is chosen by default for Integration Level settings, the preferences applied in your customer accounts will be retained. This will not overwrite the customer account-level settings during sync.
We'd request you to read our MSP user documentation to know more about the configuration profiles set-up and the third party integrations set-up in the MSP Control Panel.
Happy Monitoring!
Hi,
The configuration profiles will not get mapped automatically to monitors. When you add a new monitor or update an existing one, you can choose the desired profile for that monitor.
Hope this helps. Let us know for further queries, if any.
Happy Monitoring!
Hi Mathangi,
That is when you manually add a monitor (which we rarely do). What is the behavior for detected monitors? I noticed that when there is a Threshold profile on global level, and not a default one on customer level, the global one is picked. That makes sense. But what happens when there is one on both levels?
I also noticed that you can override the threshold values on customer level, which is good. However, when you change the global threshold value, the customer threshold value gets overwritten. It would be nice if we could chose with a toggle on customer level whether this should be the case or not.
Hi,
That is when you manually add a monitor (which we rarely do). What is the behavior for detected monitors? I noticed that when there is a Threshold profile on global level, and not a default one on customer level, the global one is picked. That makes sense. But what happens when there is one on both levels?
When there are configuration profiles (like threshold profile) created at the customer and MSP levels, the default profile will be considered (there will be no default profile at the MSP level). In case there is no default profile created, the profiles will be given preference based on alphabetical order.
I also noticed that you can override the threshold values on customer level, which is good. However, when you change the global threshold value, the customer threshold value gets overwritten. It would be nice if we could chose with a toggle on customer level whether this should be the case or not.
In this case, you can clone that particular profile at the customer level and make the necessary changes. Profiles created at the MSP level are global, such that changes will be reflected across all the customer accounts once an edit is made.
Hope this clarifies your questions. Please let us know for further queries, if any.
Happy Monitoring!