You can use ActiveGate groups to perform bulk actions on your ActiveGates, such as managing Extensions 2.0 running on ActiveGates or connecting your Cloud Foundry foundations.
-), underscores (_), and dots (.).An ActiveGate can belong to only one group. By default, an ActiveGate is assigned to the default group. You can assign an ActiveGate to a group during or after installation.
To assign an ActiveGate to a group, you can use the --set-group installation parameter during installation. Note that you can't use this parameter during an ActiveGate update. For example:
To assign ActiveGates to a group, you can use Remote configuration management (select the modify ActiveGate group action).
Alternatively, you can use the group ActiveGate configuration property. For example:
[collector]group = mygroup
For more information, see Basic rules for working with ActiveGate configuration
An ActiveGate running a remote extension needs to belong to an ActiveGate group because Dynatrace uses a group to instruct the extension where it should run. If you plan to use a single ActiveGate to run a remote extension, assign it to a dedicated group containing only that ActiveGate.
When activating the extension, you need to specify an ActiveGate group that will run your extension. You can select an ActiveGate group either during the Dynatrace Hub-based activation workflow, or specify an ActiveGate group name in the JSON payload used to activate the extension using the Dynatrace API.
When connecting Dynatrace to Cloud Foundry foundations, you specify an ActiveGate group responsible for querying Cloud Foundry for data. For more information, see Connect your Cloud Foundry foundations with Dynatrace