To manage all container-related settings, follow the instructions below.
The container monitoring rules define if deep monitoring is enabled for processes running in containers.
To add a monitoring rule
begins with)To edit a custom monitoring rule
To change the rule conditions, display the Details and make changes as needed
To delete the rule, select in the Delete column
To disable or enable the rule, change the switch setting in the Enabled column
To move the rule up or down in the list, in the Order column, select and drag the rule to a new position
Container monitoring rules are executed in the order in which they appear on the list.
There are two categories of container monitoring rules that you can enable or disable by default:
To enable/disable a custom monitoring rule
To enable/disable built-in monitoring rules
PODpause-amd64openshift-sdnBuilt-in rules are enabled by default. You can choose to disable them, but you can't edit them.
Container monitoring rules are effective only when you install OneAgent on your hosts.
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 container monitoring setup.
In Kubernetes, container monitoring rules don't affect webhook-based injection (cloudNativeFullStack, applicationMonitoring). Injection in these modes is controlled via annotations, as described in Configure monitoring for namespaces and pods.
However, once a container is injected, container monitoring rules can still influence OneAgent's activation/monitoring state, including disabling OneAgent for that process group.