SQL Monitor - 3.2
Organizing monitored servers into groups - SQL Monitor
Use the Groups page (Configuration > Groups) to organize your servers into groups sharing similar properties.
Why create a group?
Monitored servers can be grouped together so you can apply the same alert configuration settings to them more easily. For example, you may have a number of production servers on different host machines but you want them all to use the same alert settings.
You can also filter the Global Overview and Alert Inbox by group, to look at information for groups of servers at a time.
Groups are identified in the Monitored servers list by the group
icon.
Creating a group
- Go to the Configuration tab. Under Monitoring, select Groups:

You can also use the Manage groups link on the left of any overview page or the Alert Inbox.
- Click New group, enter a name and click Create.
To add servers to the group, drag and drop each one in turn onto the group name. (You cannot drag multiple selected servers.)
In the example below, the server dev-benc2 is about to be moved to the "Developer Machines" group:

Only host machines are listed:
- You cannot move individual SQL Server instances; they are moved automatically with their host machine
- If you move a cluster into a group, all its nodes and instances are moved with it
You can also select a server, and click Move. Select the destination group in the Move box.
Creating a hierarchy
You can move one group into another. For example, if you want to further organize your Production servers into several regions, you should first create your Production group, then create a group for each region and move those groups into "Production".
In the example below several sub-groups have been created for the "Production servers" group. Moving the "New York" group will also move any servers in that group.

By default, each group inherits all alert settings from the group above; so this allows you to create alert settings for all your production servers, which are applied to each region. However, you can then tweak the settings for just one of those regions, if required.
Removing a server from a group
To remove a server from a group, do one of the following:
- Drag it to All servers
- Select the server, click Move and then select All servers
Working with groups
Use the buttons above the list of groups to rename, delete or move a selected group.
Deleting a group doesn't delete the servers it contains; instead the servers are moved to the next level up in the server hierarchy.
Configuring alerts by group
One of the main benefits of adding servers to a group is that you can configure alert settings at the group level. Everything in that group inherits these settings (unless specifically customized at a lower level). Each group in the hierarchy can be customized separately.
In the example below, on the Alert settings page, different types of alerts have been customized at various levels; the Inherited from column shows which level each type of alert is customized at.

When editing the alert settings, the breadcrumbs show the full inheritance path for this type of alert. Any level with an asterisk * has been customized. In the example below, the Blocked process alert is being customized for a specific machine, but it has also been set more generically for the "Production servers" group.

For more information, see Customizing alerts.
Was this article helpful?
SQL Monitor
- Example configuration of SQL Monitor using virtualization software
- Retrieving alert settings using SQL Data Compare
- Licensing issues with SQL Monitor
- Log files in SQL Monitor
- Upgrading to a later version of SQL Monitor
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Monitor
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs

Using SQL Monitor