The Datadog Marketplace is a digital marketplace where Datadog Technology Partners can list their integrations, software, and services to Datadog users.
Before joining the Datadog Marketplace, you first need to join the Datadog Partner Network Technology Track. As a Datadog Technology Partner, you can develop an integration and create a tile listing that includes your offering.
Datadog customers can then access your tile through the Datadog app either through our Integrations page or through the Datadog Marketplace. While the Integrations page includes integrations built by Datadog and Technology Partners at no cost, the Marketplace is a commercial platform for Datadog customers and Technology Partners to buy and sell a variety of offerings, including integrations, software, and services.
Follow these steps to develop and publish your Marketplace offering:
All Technology Partners can request a dedicated sandbox Datadog account to aid in their development. To request a sandbox:
Converting an account to a developer sandbox may take up to one or two business days. Please contact Datadog Support with any questions.
In addition to this documentation, you can learn more about developing Datadog integrations by taking the following steps:
There are a few different ways to integrate with Datadog. Depending on the use case and type of integration, choose the approach that makes the most sense for your offering.
An API integration fits well for enriching and submitting data from your backend, or pulling data directly out of Datadog. API integrations also work well for building a connector between Datadog and another SaaS platform.
Note: that a Datadog API Key is required to submit data to a Datadog API endpoint, while an App Key is required for querying data from Datadog, or for creating resources within the Datadog App.
For Marketplace offerings that include a standalone SaaS or services offering, with no exchange of data, only a tile is needed. The Development Toolkit offers a command option to create tile-only scaffolding:
ddev create -t tile "<Offering Name>"
While pulling information from Datadog may also be useful, to be listed on the Datadog Integrations page or the Marketplace, the integration must be bi-directional. That is, it must also push data into Datadog.
Integrations can send the following data to Datadog:
The process for building an integration is the same for each repository, with Marketplace offerings requiring a few more files and fields (like pricing). Remember to point to the intended repository when you clone and submit your pull request.
Technology Partners can request access to the private Marketplace repository by emailing firstname.lastname@example.org.
The Datadog Development Toolkit command (
ddev) allows you to create scaffolding when you are first developing your integration, by spinning up a skeleton of all the assets and metadata for your tile.
Ensure that Python 3.8 or higher is installed.
To avoid potential environment conflicts, in the directory where you cloned the repository, create a virtual environment by running:
python3 -m pip install virtualenv --user
Install the latest released version of the Datadog Development Toolkit from PyPI by running:
python -m pip install --upgrade "datadog-checks-dev[cli]"
Note: If you are using Z shell, you may need to use escape characters:
python -m pip install --upgrade datadog-checks-dev\[cli\]
Set the location of to the cloned repository:
ddev config set marketplace /path/to/marketplace_directory ddev config set repo marketplace
ddev config set extras /path/to/integrations-extras_directory ddev config set repo extras
For standalone software and services–or if your integration is using the Datadog API and does not contain any Python code–the Development Toolkit supports a tile-only command.
integrations-extras directory you specified above, run:
ddev create -t tile "<Offering Name>"
To generate a complete integration scaffolding, from the
integrations-extras directory specified above, run:
ddev create "<Offering Name>"
The ddev commands in the previous section generate a skeleton of folders and files that make up your tile assets:
README.mdfile in the
author, and more.
manifest.jsonfields can be found in our Integrations Assets Reference
metadata.csvfields can be found in our Integrations Assets Reference.
assetsdirectory, or you can place them in a
.githubdirectory and defines the individuals or teams that are responsible for code in the repository. See Github’s documentation for help with syntax.
Each repository runs automatic tests to verify that your pull request is in good shape. You can run these same tests locally with the command
ddev validate all. Once the PR is passing all checks, our Engineering team will begin their review, where they will identify blockers to release, as well as make suggestions around best practices.
If you need access to Azure DevOps for the Marketplace repository, please leave a comment in the PR and our engineering team will provide access.
When the pull-request tile has been approved by our Engineering and Product teams, your tile will be enabled for your sandbox account. This will allow you to validate and view the integration tile in the Datadog Marketplace and make changes before it goes live.
Once an official bi-directional integration is live, Technology Partners have the option of meeting with Datadog’s Partner Marketing Team to coordinate a joint go-to-market strategy, including:
Please reach out to us at email@example.com if you have any questions.
Additional helpful documentation, links, and articles: