/integrations-core

Core integrations of the Datadog Agent

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

Datadog Agent Integrations - Core

Build status Build status Coverage status Documentation Status

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 (Nov 20 2018), can trigger a build by signing a commit:

  • 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
  • Hippolyte Henry
    • 87D5 2666 ECBF 2459 9D5A 594F F7AC E411 B85D 518C
    • 31EE F81D 7F71 6E35 83F2 4095 55D1 30B4 49D2 BD26
  • Ofek Lev
    • C295 CF63 B355 DFEB 3316 02F7 F426 A944 35BE 6F99
    • D009 8861 8057 D2F4 D855 5A62 B472 442C B7D3 AF42
  • Greg Meyer
    • 989A 83AA 3C99 E86D DB9E EE69 598E 38E0 370E B759
    • E145 39B1 BE48 615B FFE5 E7D2 4EA8 2631 E127 97FC
  • Nicholas Muesch
    • 6E09 1A53 0468 B148 54BB 6CCE 831C 23C4 9BBE 61F8
    • BACE F480 6D0B 4FBE D227 DC3B C0E2 8E5E 241E D25A
  • Massimiliano Pippi
    • BE9C 5131 8EED C03F E901 F256 C2C8 965F 07D0 A23D
    • 69CA DE35 4030 5312 54AF 170C 50A7 66D9 4DFC 27CC
  • Greg Zussa
    • D24D 57CE 96BD F8C2 9BB0 BEAB C783 0ECB 08F8 8C74
    • 3936 7937 7466 5878 C67A 50E9 3C67 09D5 583F B57C