[ Datadog ] Host Monitor

All Datadog Agents can check their status using datadog.agent.up.

1. Pick hosts by name or tag

   

   In the first Select Box, select the host to monitor using the tag method. (AND logic applies when selecting multiple conditions) If All Monitored Hosts is selected, all hosts will be targeted.
   In the second Select Box, select the host to be excluded from the hosts selected in the first Select Box using the tag method. (OR logic applies when selecting multiple conditions)

2. Set alert conditions
   In this section, select between Check Alert or Cluster Alert.

   1. Check Alert

      

      
      An alert is generated when a host stops reporting for a specified period.
      - Alerts are generated for each group selected in the select group.
      - The time period for which reporting stops can be specified. (Default: 2 minutes)
      - An auto-clear function can be used to automatically resolve the alert after a specific time.

   2. Cluster Alert

      

      An alert is generated when a certain percentage of hosts stop reporting for a specified period.
      - Determines whether to group hosts by tags.
      Ungrouped calculates the status percentage for all included hosts.
      Grouped calculates the status percentage for each group.
      - Select the percentage for Alert and Warning thresholds.
      - Specify the time that serves as the criterion for stopping reports. (Default: 2 minutes)
      - An auto-clear function can be used to automatically resolve the alert after a specific time.
      - If Grouped is selected, specify the delay time before the alert applies when a new group is added. (Before evaluating new groups setting)

3. Notify your team
   Select the recipients (email) to receive alerts or choose channels set in Integration from the list.

   

   • Alert Title: The title of the message transmitted when an alert occurs.
     - Example: [Warning] [{{service.name}}] {{host.name}} server is unresponsive.

   • Alert Message
     - The content of the message transmitted when an alert occurs.
     - Example

     {{#is_alert}}
     
     Occurrence Time (ST): {{local_time 'last_triggered_at' 'Asia/Seoul'}}
     
     [Critical] [{{env.name}}][{{service.name}}]  {{host.name}} ({{host.ip}}) server is unresponsive.
     
     {{/is_alert}}
     
     {{#is_alert_recovery}}
     
     Occurrence Time (KST): {{local_time 'last_triggered_at' 'Asia/Seoul'}}
     
     [Critical Resolved] [{{env.name}}][{{service.name}}]  {{host.name}} ({{host.ip}}) server unresponsiveness has been resolved.
     
     {{/is_alert_recovery}}

   • Use Message Template Variables
     You can check how to use templates and variables available in the Alert title and Message body.
     Reference available variables: https://docs.datadoghq.com/monitors/notify/variables/?tab=is_alert

   • Notify your services and your team members settings
     Integrated notification channels such as opsgenie / slack / TEAMS / webhook and email will be displayed.
     Please configure the channel or target email to propagate the alert.

   • Content displayed settings (Message composition settings)
     Configure whether to include automatically added content such as query/snapshot in the Message.

   • Include Triggering tags in notification title settings
     Displays tags related to the triggered alert in the title of the propagated Message.

   • Aggregation settings
     If a selected Group exists in Set alert conditions, it is automatically selected as a multi-alert.

   • Renotification settings
     If an Alert (Warning) or Nodata persists, re-alerts will be sent at the selected time intervals.

   • Tags settings
     Set tags for monitors that can be used when searching in Manage Monitors or configuring the Downtime schedule.

   • Priority settings
     Set the severity (importance) of alerts from P1 to P5.
     Priority settings (standardization is in progress based on the criteria below)