devops:monitoring:datadog:integrations
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| devops:monitoring:datadog:integrations [2025/02/14 10:13] – 85.219.17.206 | devops:monitoring:datadog:integrations [2025/02/14 10:15] (current) – 85.219.17.206 | ||
|---|---|---|---|
| Line 87: | Line 87: | ||
| ddev create Awesome | ddev create Awesome | ||
| - | |||
| - | Write an Agent check | ||
| - | |||
| - | At the core of each Agent-based integration is an Agent Check that periodically collects information and sends it to Datadog. | ||
| - | |||
| - | Checks inherit their logic from the AgentCheck base class and have the following requirements: | ||
| - | |||
| - | Integrations running on the Datadog Agent v7 or later must be compatible with Python 3. Integrations running on the Datadog Agent v5 and v6 still use Python 2.7. | ||
| - | Checks must derive from AgentCheck. | ||
| - | Checks must provide a method with this signature: check(self, instance). | ||
| - | Checks are organized in regular Python packages under the datadog_checks namespace. For example, the code for Awesome lives in the awesome/ | ||
| - | The name of the package must be the same as the check name. | ||
| - | There are no restrictions on the name of the Python modules within that package, nor on the name of the class implementing the check. | ||
| - | |||
| - | Implement check logic | ||
| - | |||
| - | For Awesome, the Agent Check is composed of a service check named awesome.search that searches for a string on a web page. It results in OK if the string is present, WARNING if the page is accessible but the string was not found, and CRITICAL if the page is inaccessible. | ||
devops/monitoring/datadog/integrations.1739527998.txt.gz · Last modified: 2025/02/14 10:13 by 85.219.17.206
