Process Check Monitor
A process check monitor watches the status produced by the Agent check
process.up. At the Agent level you can configure your check thresholds based on the number of matching processes.
To create a process check monitor in Datadog, use the main navigation: Monitors –> New Monitor –> Process Check.
Pick a process
From the drop-down list, select a process to monitor. Filter the list by entering your search criteria.
Pick monitor scope
Select the hosts to monitor by choosing host names, tags, or choose
All Monitored Hosts. Only hosts or tags reporting a status for the selected process are displayed. If you need to exclude certain hosts, use the second field to list names or tags.
- The include field uses
AND logic. All listed host names and tags must be present on a host for it to be included.
- The exclude field uses
OR logic. Any host with a listed name or tag is excluded.
Set alert conditions
A check alert tracks consecutive statuses submitted per check grouping and compares it to your thresholds. For process check monitors, the groups are static:
Set up the check alert:
Trigger the alert after selected consecutive failures:
Each check run submits a single status of
CRITICAL. Choose how many consecutive runs with the
CRITICAL status trigger a notification. For example, your process might have a single blip where connection fails. If you set this value to
> 1, the blip is ignored but a problem with more than one consecutive failure triggers a notification.
Resolve the alert after selected consecutive successes:
Choose how many consecutive runs with the
OK status resolves the alert.
A cluster alert calculates the percent of process checks in a given status and compares it to your thresholds.
Set up a cluster alert:
Decide whether or not to group your process checks according to a tag.
Ungrouped calculates the status percentage across all sources.
Grouped calculates the status percentage on a per group basis.
Select the percentage for alert and warn thresholds. Only one setting (alert or warn) is required.
Each check tagged with a distinct combination of tags is considered to be a distinct check in the cluster. Only the status of the last check of each combination of tags is taken into account in the cluster percentage calculation.
For example, a cluster check monitor grouped by environment can alert if more that 70% of the checks on any of the environments submit a
CRITICAL status, and warn if more that 70% of the checks on any of the environments submit a
Advanced alert conditions
See the Monitor configuration documentation for information on No data, Auto resolve, and New group delay options.
For detailed instructions on the Say what’s happening and Notify your team sections, see the Notifications page.
Additional helpful documentation, links, and articles: