{"id":40861,"date":"2022-12-21T14:59:15","date_gmt":"2022-12-21T14:59:15","guid":{"rendered":"https:\/\/www.n-able.com\/?p=40861"},"modified":"2025-02-20T21:58:56","modified_gmt":"2025-02-20T21:58:56","slug":"making-rmm-notifications-work-for-you-in-n-central","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/pt-br\/blog\/making-rmm-notifications-work-for-you-in-n-central","title":{"rendered":"Making RMM Notifications work for you in N‑central"},"content":{"rendered":"

Over the years I have spoken with many prospects and partners about changing RMM solutions<\/span><\/a>. When I\u2019d ask the question \u201cWhy did you change?\u201d, often the answer would be that their previous solution was too noisy when it came to generating email notifications. The sheer volume of notifications that some RMM solutions generate can make it very difficult for users to see the wood from the trees, resulting in important notifications being missed.\u00a0 <\/span><\/p>\n

N‑central<\/a><\/span> has a good balance when it comes to notifications, with approximately 36 pre-configured out of the box. In this blog we are going to look at how N‑central notifications<\/span><\/a> work, and how you can tweak them so that they are of greater value to you and your organization.<\/span><\/p>\n

How do N‑central notifications work?<\/span><\/h2>\n

Before we started to make changes to the default notifications, lets take a moment to ensure we understand how notifications work. A Notification Profile<\/span><\/a> is comprised two elements: <\/span><\/p>\n

    \n
  1. The Profile Details tab\u2014Here you can configure who is notified and when they are notified<\/span><\/li>\n
  2. The Trigger Details tab\u2014This allows you to configure what causes the notification to be sent<\/span><\/li>\n<\/ol>\n

    By adding or removing recipients from the Profile Details tab, you can ensure that RMM notifications are only being sent to those that need them. Also, if you have no recipients selected on the profile details tab, then no notifications will be sent.<\/span><\/p>\n

    On the Trigger Details tab, you\u2019ll see the services\/service instances and the status that will cause the notification to be sent. Each of these triggers is applied to devices via rules, so if you remove the selected rules from the trigger, it will also stop notifications being sent (you can leave everything else in the profile intact). This is useful if you have multiple triggers in a notification profile, but you only want to temporarily disable some.<\/span><\/p>\n

    Streamlining Notifications<\/span><\/h2>\n

    Now that we know how notifications work, it\u2019s time to review how you have configured your notifications, and streamline them to suit your needs.\u00a0 <\/span><\/p>\n

    Notification Profiles are one of the few areas of N‑central where you can delete the out of the box configurations at the SO level. If you\u2019re planning on doing this and thinking to yourself, \u201cI\u2019ll just start from the ground up\u201d\u2014DON\u2019T.\u00a0 You\u2019ll be creating unnecessary work for yourself. The default N‑central notifications are there for a reason: they are the ones that are most commonly used by users. <\/span><\/p>\n

    Instead of starting from the ground up, go through each notification profile to understand what it alerts on. For those you don\u2019t want to receive, as mentioned above, simply remove any selected recipients from the profiles tab. You can also rename these notification profiles to include \u201cNot Currently in Use\u201d, so you and your colleagues know what\u2019s going on. By leaving unused profiles there and not deleting them, you can easily bring them into use in the future if you need to.<\/span><\/p>\n

    So, it\u2019s pretty easy to get a handle on notifications you don\u2019t want to receive, but what about the notifications that you want for some clients but not for others? Maybe you have different tiers of support packages and you want to prioritise notifications for your \u201cGold Level\u201d clients, or maybe you have some break\/fix clients in your N‑central instance that shouldn\u2019t generate notifications in the same way as your managed clients\u2026 how do you handle that?\u00a0 <\/span><\/p>\n

    By default, as mentioned above, the Notification Profiles target devices via rules, and the rules we use are prebuilt rules like Laptops, Windows\/Server, Windows etc. that also, by default, deploy monitoring templates and apply basic configuration. In order to apply different Notifications Profiles to different clients in N‑central, you will need to separate out the monitoring portion of the rule from the notification portion. While this might feel of a pain, it\u2019s short-term pain for long-term gain.\u00a0 Having rules specifically for notification purposes will give you far more flexibility when if comes to configuring notifications for your clients.\u00a0 <\/span><\/p>\n

    To implement this, follow these steps with you existing rules:<\/span><\/p>\n