The Datadog Marketplace is a digital marketplace where Datadog Technology Partners can list their data integrations, software, and professional 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 a data integration, a Datadog App, or list your SaaS license or professional services offering.
Datadog customers can then access your tile through the Datadog site either through the Integrations page or through the Datadog Marketplace. While the Integrations page includes data integrations and Datadog Apps 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 data integrations, Datadog Apps, software, and professional services.
Follow these steps to develop and publish your offering on the Integrations page or Datadog Marketplace:
All Technology Partners can request a dedicated sandbox Datadog account to aid in their development. To request a sandbox:
Creating a developer sandbox may take up to one or two business days. Contact Datadog Support with any questions.
Note: If you are already a member of a Datadog organization (including a trial org), you may need to switch to your newly created sandbox, following the instructions on switching between orgs.
Once your sandbox is created, you can invite new members from your organization to collaborate with.
In addition to this documentation, you can learn more about developing Datadog integrations and other offerings by taking the following steps:
There are a few different types of offerings that you can list on the Datadog Integrations or Marketplace pages:
Regardless of the type of offering that you are developing, a tile that represents your listing needs to be created for either the Marktplace or Integrations page. You can see an example of a Marketplace tile below:
Depending on the use case, choose the approach that makes the most sense for your offering.
If you’re developing an offering that does not use the Datadog Agent, such as a Datadog App, SaaS license, professional service, or an API-based integration, you will need to create a tile-only listing.
For general information, read Introduction to Agent-based Integrations.
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.
Since API integrations do not use the Datadog Agent to collect data, you will need to create a tile only listing once your development work is complete.
Note: A Datadog API key is required to submit data to a Datadog API endpoint, while an application key is required for querying data from Datadog, or for creating resources within the Datadog site.
Datadog Apps are custom dashboard widgets that are developed in the Datadog Developer Platform. Once your Datadog App is ready to publish, you will need to create a tile only listing on either the Marketplace or Integrations page.
For offerings that are not using the Datadog Agent to collect data, only a tile is needed. Tile only listings include SaaS licenses and professional services offerings, Datadog Apps, and API-based integrations that require users to do all of the integration configuration and installation outside of Datadog.
The Datadog Development Toolkit offers a command option to create tile-only scaffolding: ddev create -t tile -v2 "<Offering Name>". When this command is used, you’ll only receive the files related to populating your tile, rather than the files used to build out a full Agent-based data integration.
While pulling information from Datadog may be useful, integrations must be bi-directional. That is, it must also push data into Datadog.
Integrations can send the following data to Datadog:
Note: A bi-directional data integration is not required for Marketplace tile-only listings, such as standalone SaaS licenses and professional services offerings.
Datadog integrations can be developed for either the private Marketplace repository or open-source integrations-extras repository.
The process for building a data 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 submit your pull request.
Technology Partners can request access to the private Marketplace repository by emailing marketplace@datadog.com.
The Datadog Development Toolkit command (ddev) allows you to create scaffolding when you are first developing your data 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
integrations-extrasddev config set extras /path/to/integrations-extras_directory
ddev config set repo extras
For standalone SaaS licenses, Datadog Apps, and professional services–or if your data integration is using the Datadog API and does not use the Datadog Agent–the Development Toolkit supports a tile-only command.
In the marketplace or integrations-extras directory you specified above, run:
ddev create -t tile -v2 "<Offering Name>"
To generate a complete data integration scaffolding, from the marketplace or integrations-extras directory specified above, run:
ddev create -v2 "<Offering Name>"
The ddev commands in the previous section generate a skeleton of folders and files that make up your tile assets:
README.md file in the images folder.README.md file. Instead, these images should be placed in the media carousel by adding them to the media object in your manifest.json file.display_name, public_title, author, and more.manifest.json fields can be found in the Integrations Assets Reference.metadata.csv fields can be found in the Integrations Assets Reference.assets directory, or you can place them in a logos sub-directory under assets..github directory and defines the individuals or teams that are responsible for code in the repository. See GitHub’s documentation About code owners for help with syntax.If you’ve followed the commands on this page to create your listing using the -v2 flag, you will have access to a media carousel on your tile. The media carousel has specific requirements for images and videos:
vimeo_link that you can add to your manifest.json file to include the video in your listing.Submit a pull request containing all of your files either to the Marketplace repository, or to Integrations Extras repository.
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, the Datadog Engineering team reviews to identify blockers to release and makes suggestions around best practices.
If you need access to Azure DevOps for the Marketplace repository, leave a comment in the PR to request access.
When the Datadog Engineering and Product teams approve your pull-request, the tile is enabled for your sandbox account. This allows you to validate and view your tile in the Datadog Marketplace and make changes before it goes live.
Once a Marketplace tile is live, Technology Partners have the option of meeting with Datadog’s Partner Marketing Team to coordinate a joint go-to-market strategy, including:
Email marketplace@datadog.com if you have any questions.
Additional helpful documentation, links, and articles:
