/integrations-core

Core integrations of the Datadog Agent

Primary LanguagePythonBSD 3-Clause "New" or "Revised" LicenseBSD-3-Clause

Datadog Agent Integrations - Core

Build status Coverage status Documentation Status Code style - black

This repository contains the Agent Integrations (also known as checks) that Datadog officially develops and supports. To add a new integration, please see the Integrations Extras repository and the accompanying documentation.

The Datadog Agent packages are equipped with all the Integrations from this repository, so to get started using them, you can simply install the Agent for your operating system. The AGENT_CHANGELOG file shows which Integrations have been updated in each Agent version.

Integrations as Python wheels

When working with an integration, you will now be dealing with a more structured python project. The new structure should help keep a more sane and modular codebase. To help with the transition, please take a look at the following map to understand where everything falls into place in the new approach.

FORMER LOCATION NEW LOCATION
{integration}/check.py {integration}/datadog_checks/{integration}/*.py
{integration}/test_check.py {integration}/tests/*.py
n/a {integration}/setup.py

Now that integrations are cleanly defined as python packages, we will soon be able to ship them as Python wheels that will be pip-installable in the Python environment embedded into the Datadog Agent. This presents a paradigm change in the way we will be delivering standalone integration upgrades, moving away from OS-specific packages to idiomatic Python package delivery.

Contributing

Working with integrations is easy, the main page of the development docs contains all the info you need to get your dev environment up and running in minutes to run, test and build a Check. More advanced API documentation can be found here

Reporting Issues

For more information on integrations, please reference our documentation and knowledge base. You can also visit our help page to connect with us.

GPG public keys

For those whom it may concern, the following is a list of GPG public key fingerprints known to correspond to developers who, at the time of writing (Dec 2 2019), can trigger a build by signing metadata:

  • Christine Chen
    • 57CE 2495 EA48 D456 B9C4 BA4F 66E8 2239 9141 D9D3
    • 36C0 82E7 38C7 B4A1 E169 11C0 D633 59C4 875A 1A9A
  • Dave Coleman
    • 8278 C406 C1BB F1F2 DFBB 5AD6 0AE7 E246 4F8F D375
    • 98A5 37CD CCA2 8DFF B35B 0551 5D50 0742 90F6 422F
  • Mike Garabedian
    • F90C 0097 67F2 4B27 9DC2 C83D A227 6601 6CB4 CF1D
    • 2669 6E67 28D2 0CB0 C1E0 D2BE 6643 5756 8398 9306
  • Thomas HervĂ©
    • 59DB 2532 75A5 BD4E 55C7 C5AA 0678 55A2 8E90 3B3B
    • E2BD 994F 95C0 BC0B B923 1D21 F752 1EC8 F485 90D0
  • Ofek Lev
    • C295 CF63 B355 DFEB 3316 02F7 F426 A944 35BE 6F99
    • D009 8861 8057 D2F4 D855 5A62 B472 442C B7D3 AF42
  • Florimond Manca
    • B023 B02A 0331 9CD8 D19A 4328 83ED 89A4 5548 48FC
    • 0992 11D9 AA67 D21E 7098 7B59 7C7D CB06 C9F2 0C13
  • Julia Simon
    • 4A54 09A2 3361 109C 047C C76A DC8A 42C2 8B95 0123
    • 129A 26CF A726 3C85 98A6 94B0 8659 1366 CBA1 BF3C
  • Florian Veaux
    • 3109 1C85 5D78 7789 93E5 0348 9BFE 5299 D02F 83E9
    • 7A73 0C5E 48B0 6986 1045 CF8B 8B2D 16D6 5DE4 C95E
  • Alexandre Yang
    • FBC6 3AE0 9D0C A9B4 584C 9D7F 4291 A11A 36EA 52CD
    • F8D9 181D 9309 F8A4 957D 636A 27F8 F48B 18AE 91AA