How to configure alerts to be sent to different users for different servers

Different server groups have different use cases and eventually, different directly responsible individuals (DRIs). An alert from a server should be directed to the proper DRI to ensure prompt action and minimized alert fatigue. With Site24x7, you can direct the alerts for a particular server or group of servers to be sent to the responsible personnel. 

Consider a use case. Zylker Corp has three servers—an app server named AppProduction, a database server named DBProduction, and a file server named DiskProduction. Each server has its own administrator responsible for its seamless functioning. The alerts from one server should not bother the other two administrators. Zylker was able to handle this with configuration rules and user alert groups. 

Zylker created three user alert groups named AppServer, DBServer, and FileServer with the respective administrators as the users. 

Then, via configuration rules, Zylker has set a rule that all servers with the name starting with App should be associated with the AppServer user profile. After clicking Save, all existing servers starting with the name App will be associated with the  AppServer user alert group, and any alerts related to this server will be sent only to the administrator under the AppServer user alert group. 

In the future, when Zylker adds more app servers, this rule will automatically associate the servers with name starting with App to the AppServer user alert group. This same strategy can be used for other servers and server groups.

Targeted alerts improve your IT infrastructure quality, reduce the mean time to repair (MTTR), and reduce alert fatigue.

To learn more about how configuration rules can enable zero-touch configuration in your IT infrastructure, here is a detailed blog on configuration rules. You can also check out these help documents for setting up configuration rules and user alert groups.

• Related Articles

• Troubleshooting false positive alerts in monitoring

  Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...

• Monitor and validate DNS IP changes using regex

  DNS administrators often monitor their DNS servers to detect changes in domain resolution and ensure IP mappings remain secure and accurate. Problem When your organization adds or modifies an IP address for your domain name, it’s critical to: Be ...

• How to configure the NGINX status page for monitoring NGINX performance

  The NGINX plugin uses the NGINX status page to pull the performance metrics of the NGINX server. You may encounter the following errors while installing the NGINX plugin integration: Error_code : HTTP Error 404: This error usually indicates that the ...

• Executables and scripts to allow for Windows server monitoring

  One of the reasons you could not enable Site24x7 server monitoring could be your organization's group policy denying access to the executables, scripts, and batch files associated with Site24x7 server monitoring. Mark the following executables, ...

• No data for service and process in Windows server monitor

  If you see "No Data" for process and service metrics (such as CPU or memory usage of monitored services) in the Site24x7 Windows server monitor user interface, follow the troubleshooting steps below. Run PowerShell Commands Open PowerShell as ...