Set up process group monitoring

Installing OneAgent provides you with process group monitoring capabilities such as:

  • Automatic monitoring of all process groups that are detected in your environment after you restart all processes that have been running during the OneAgent installation.
  • End-to-end visibility into requests of all auto-detected server-side services, including database services.
  • A fully automated monitoring process with no configuration required, thus simplifying monitoring of large-scale environments with hundreds of hosts and thousands of processes, where manual monitoring configuration of all entities isn't feasible.

Optionally, you can set up monitoring rules to selectively specify which processes Dynatrace monitors. For example, consider the following common scenarios:

  • You have a number of unimportant or short-lived processes that you don’t want to monitor at the code level.
  • You aren't able to run deep monitoring on applications that belong to your customers and are out of your control.
  • You want to have better control over which processes are monitored.
  • You want to perform deep monitoring on .NET and Go processes (Dynatrace doesn't automatically perform deep monitoring on them, as there are many arbitrary processes that rely on these processes). For instance you want to monitor all ASP.NET applications and all Go and .NET core applications running on Cloud Foundry or Kubernetes.

You can set up monitoring rules in Settings > Processes and containers > Process group monitoring.

Enable automatic deep monitoring

  • By default, automatic deep monitoring is set to On to enable Dynatrace OneAgent to run deep monitoring on all detected processes (unless you specify exceptions for specific processes or create rules that define exceptions). Disable this setting only if your company policies require it.

  • Set to Off if you want Dynatrace OneAgent to run deep monitoring only for processes that are specified explicitly or that are covered by a deep monitoring rule. You can then manually enable monitoring at the process level or process group level, or choose to define rules about what you want to monitor.

Note: Deep monitoring can be disabled only if all installed OneAgents in your monitored environment are at version 1.123 or higher.

How process monitoring rules are applied

Enable automatic deep monitoring doesn’t take precedence over any individual process monitoring rules you may have set up. If a process monitoring rule indicates that Dynatrace should monitor a certain process, and Enable automatic deep monitoring is Off, the individual rule will take precedence and Dynatrace will monitor the respective process. Therefore, each process monitoring rule is an exception to the general monitoring policy.

Define custom process monitoring rules

Custom process monitoring rules give you fine-grained control over which processes OneAgent monitors with an approach that scales easily within large environments. You don’t need to adjust your system configuration, and a few rules can cover thousands of processes.
For example, the second rule in the image below tells Dynatrace not to monitor any Java process that is started by a JAR file that contains the string cmdlauncher.

Example custom process monitoring rules

To add a custom monitoring rule

  1. Select Process monitoring rules.
  2. Select Add a new rule.
  3. Set the Behavior by selecting whether you want Dynatrace to monitor the process.
  4. Set the Condition by selecting
    • The rule property (see process group detection rules for the list of properties).
    • The operator (for example, contains).
    • The value for the operator.
  5. Select Create rule to save your changes and add the new rule to your list of custom process monitoring rules.

For example, you can create a rule that OneAgent shouldn’t be injected into any process in Cloud Foundry spaces that contain the string customer.
Example: create custom process monitoring rule

To configure a custom monitoring rule

  1. Select the rule you want to configure.
  2. You can edit, delete, or disable/enable the rule, and you can move it up or down in the list of custom rules.
    Note: Process monitoring rules are executed in the order on the list. Move the rules up/down to change the order.
  3. Select Save changes to apply your changes.

Enable or disable built-in process monitoring rules

Built-in rules refer to processes that Dynatrace monitors by default. These are

  • All .NET and Go Kubernetes applications

  • All .NET and Go Cloud Foundry applications

  • All .NET and Go applications deployed in Docker containers

  • ASP.NET Core applications started by IIS

  • Core components of Cloud Foundry written in Go

  • Caddy—a web server written in Go

  • InfluxDB—a timeseries database written in Go

To see the list of built-in rules, select Built-in process monitoring rules.
Built-in rules are enabled by default. You can opt to disable them, but you can't edit the rules.

Note: These built-in rules don't cover your own .NET and Go applications unless those applications are deployed in containers, Cloud Foundry, or Kubernetes. If this is not the case for your .NET and Go applications, you should add your own .NET and Go applications as custom monitoring rules.

Dynatrace doesn’t automatically carry out deep monitoring of all .NET and Go processes. Many popular applications such as Microsoft Office make use of .NET, and many common infrastructure components are written in Go, so Dynatrace performs deep monitoring of .NET and Go processes only if you explicitly enable it or if they are covered by monitoring rules.

Limitations

  • Deep monitoring rules only affect service- and code-level monitoring.

  • Deep monitoring rules are only effective when you install OneAgent on your hosts or images.

  • Application-only integrations without a full OneAgent installation don’t support monitoring rules. However, in such situations, the integrations themselves effectively provide the same level of control over your process monitoring setup.

  • Rules may work on earlier versions of OneAgent, but they’re only supported for OneAgent version 1.151+.