Groups are central to how MySQL Enterprise Monitor operates. For example, an Asset (such as a host or MySQL instance) that is added to a group will automatically inherit all Advisors that are scheduled for that group. And moving an Asset to a different group will automatically update the schedules, accordingly.
In MySQL Enterprise Monitor 2.3, schedules were set per Asset, and not per group.
Each panel in the Service Manager allows you to distinguish between groups (e.g., graph a specific group), and groups help configure the handling of Events and Advisors.
MySQL Enterprise Monitor has two different types of server groups:
Ad hoc: You manually construct these
groups, which are typically grouped using hosts and MySQL
instances. For example, you might define "Development" and
"Production" server groups.
Replication: MEM automatically generates a
grouping for the replication topology, if present.
The text is captured as-is in the text field when defining a group name. For example, HTML entities are not converted.
In the following example we will set up two Server groups, and define them as the "Development" and "Production":
For more information about configuring groups, see Section 14.4, “MySQL Instances”.