OneAgent version 1.329+
In large, dynamic environments, the number of processes running on your hosts can become overwhelming. Dynatrace automatically organizes these processes into process groups so you can monitor them together. When the default grouping doesn't match how you want to view your processes, process grouping rules let you split, merge, or exclude process groups using rules based on process properties detected by OneAgent.
Process grouping rules define how OneAgent groups monitored processes into process groups (PGs) and process group instances (PGIs). You can apply rules at the environment, host group, Kubernetes cluster, and host levels.
Simple detection rules, advanced detection rules, and declarative process grouping are now deprecated. Process grouping rules replace all three. You can migrate all valid detection rules to the new format. For details, see Migrate to process grouping rules.
Rules configured on scopes lower than environment and Kubernetes cluster, that is, on host group or host level, might currently not work reliably in cloud-native full-stack monitoring.
Be cautious when using process grouping rules, as changes may cause compatibility issues with extensions or plugins that depend on process group instance (PGI) names or technologies. Such modifications can lead to malfunctions and loss of data or metrics in monitored processes.
To minimize the risk of compatibility issues when setting up process grouping rules, you can:
For configuration steps, see Configure process grouping rules.
Consider the following scenario:
Solution: Match a substring of the command line.
Consider the following scenario:
Solution: Group processes by the environment variable property.
Consider the following scenario:
Solution: Group processes by the Node.js script name property.
Learn how to migrate your process groups and process group instances to process grouping rules.
Learn how to split and merge process groups and process group instances through process grouping rules.