Checks de service

L’endpoint de check de service vous permet d’envoyer des statuts de check afin de les utiliser avec les monitors. Les messages de check de service ne peuvent pas dépasser 500 caractères. Si un check est envoyé avec un message contenant plus de 500 caractères, seuls les 500 premiers caractères seront affichés. Les messages sont envoyés uniquement pour les checks dont le statut est Critical ou Warning, mais pas pour les checks dont le statut est OK.

  • [En savoir plus sur les monitors de check de service.][1]
  • [En savoir plus sur les monitors de check de processus.][2]
  • [En savoir plus sur les monitors de check réseau.][3]
  • [En savoir plus sur les monitors de check custom.][4]
  • [En savoir plus sur les checks de service et les codes de statut.][5]

[1] : https://docs.datadoghq.com/monitors/types/service_check/ [2] : https://docs.datadoghq.com/monitors/create/types/process_check/?tab=checkalert [3] : https://docs.datadoghq.com/monitors/create/types/network/?tab=checkalert [4] : https://docs.datadoghq.com/monitors/create/types/custom_check/?tab=checkalert [5] : https://docs.datadoghq.com/developers/service_checks/

POST https://api.ap1.datadoghq.com/api/v1/check_runhttps://api.datadoghq.eu/api/v1/check_runhttps://api.ddog-gov.com/api/v1/check_runhttps://api.datadoghq.com/api/v1/check_runhttps://api.us3.datadoghq.com/api/v1/check_runhttps://api.us5.datadoghq.com/api/v1/check_run

Présentation

Envoyez une liste de checks de service.

Remarque : une clé d’API valide est requise.

Requête

Body Data (required)

Corps de requête pour l’envoi de check de service.

Expand All

Champ

Type

Description

check

string

The check.

host_name

string

The host name correlated with the check.

message

string

Message containing check status.

status

enum

The status of a service check. Set to 0 for OK, 1 for warning, 2 for critical, and 3 for unknown. Allowed enum values: 0,1,2,3

tags

[string]

Tags related to a check.

timestamp

int64

Time of check.

[
  {
    "check": "app.ok",
    "host_name": "host",
    "status": 0,
    "tags": [
      "test:ExampleServiceCheck"
    ]
  }
]

Réponse

Payload accepted

The payload accepted for intake.

Expand All

Champ

Type

Description

status

string

The status of the intake payload.

{
  "status": "ok"
}

Bad Request

Error response object.

Expand All

Champ

Type

Description

errors [required]

[string]

Array of errors returned by the API.

{
  "errors": [
    "Bad Request"
  ]
}

Authentication Error

Error response object.

Expand All

Champ

Type

Description

errors [required]

[string]

Array of errors returned by the API.

{
  "errors": [
    "Bad Request"
  ]
}

Request timeout

Error response object.

Expand All

Champ

Type

Description

errors [required]

[string]

Array of errors returned by the API.

{
  "errors": [
    "Bad Request"
  ]
}

Payload too large

Error response object.

Expand All

Champ

Type

Description

errors [required]

[string]

Array of errors returned by the API.

{
  "errors": [
    "Bad Request"
  ]
}

Too many requests

Error response object.

Expand All

Champ

Type

Description

errors [required]

[string]

Array of errors returned by the API.

{
  "errors": [
    "Bad Request"
  ]
}

Exemple de code

                          # Curl command
curl -X POST "https://api.ap1.datadoghq.com"https://api.datadoghq.eu"https://api.ddog-gov.com"https://api.datadoghq.com"https://api.us3.datadoghq.com"https://api.us5.datadoghq.com/api/v1/check_run" \ -H "Accept: application/json" \ -H "Content-Type: application/json" \ -H "DD-API-KEY: ${DD_API_KEY}" \ -d @- << EOF [ { "check": "app.ok", "host_name": "host", "status": 0, "tags": [ "test:ExampleServiceCheck" ] } ] EOF

PREVIEWING: emmett.butler/dd-trace-api
Your Privacy Choices