The Datadog Marketplace is a digital marketplace where Datadog Technology Partners can list their integrations, software, and services to Datadog users.
Join the Datadog partner network
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 or create a tile only listing that includes your SaaS or 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 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 Integrations page or Marketplace offering:
Apply for a sandbox account
All Technology Partners can request a dedicated sandbox Datadog account to aid in their development. To request a sandbox:
- Log into the Datadog Partner Portal.
- On your personal homepage, click on the “Learn More” button under “Sandbox Access”.
- Select “Request Sandbox Upgrade”.
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.
Develop your integration or create a Marketplace tile only listing
In addition to this documentation, you can learn more about developing Datadog integrations by taking the following steps:
- Choose the type of Marketplace offering you would like to list
- Build a bi-directional integration
- Clone the Marketplace repository or fork the Integrations Extras repository
- Install the Datadog Development Toolkit
- Populate the tile scaffolding with metadata and out-of-the-box assets (like dashboards and monitors)
- Submit a pull-request
- Approve tile for release
Choose an integration type or tile only listing
There are a few different ways to list on the Datadog Integrations or Marketplace pages. Depending on the use case, choose the approach that makes the most sense for your offering.
- A OpenMetrics check is suitable for gathering telemetry data from existing applications that expose metrics using the Open Metrics standard.
- A Python check is suitable for monitoring services or products that do not expose metrics in a standard format. The Python check is used to collect telemetry data from various APIs or command line tools.
- DogStatsD is suitable for applications that already emit telemetry using the StatsD protocol. Datadog adds additional Datadog-specific extensions to the StatsD protocol including:
- Histogram Metric Type
- Service Checks
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: 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.
Tile only listing
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>"
Build a bi-directional integration
While pulling information from Datadog may also be useful, integrations must be bi-directional. That is, it must also push data into Datadog.
Integrations can send the following data to Datadog:
- Service Checks
- Security Events
Note: A bi-directional 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 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
Tile only listing
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 -v2 "<Offering Name>"
To generate a complete integration scaffolding, from the
integrations-extras directory specified above, run:
ddev create -v2 "<Offering Name>"
Populate the tile scaffolding
The ddev commands in the previous section generate a skeleton of folders and files that make up your tile assets:
- Include “Overview,” “Setup,” and “Support” sections with H2 headings (## in Markdown).
- The “Overview” heading should clearly describe the value your offering provides users, as well as how it can be used together with Datadog for more comprehensive observability. It is recommended to add images of your software or dashboards in action. This section is displayed in the “Overview” tab of your tile.
- The “Setup” heading should provide straightforward configuration steps for users to install or use your offering. This section is displayed in the “Configuration” tab of your tile.
- The “Support” heading should identify a contact for support, and possibly an option to submit product feedback. This section is displayed in the “Support” tab of your tile.
- Store all images used in your
README.md file in the
- Note: Don’t include spaces in the name of image files.
- JSON object including elements for
author, and more.
- More information about
manifest.json fields can be found in the Integrations Assets Reference.
- Details on the pricing object are described in the private Marketplace README.
- Contains a list of the out-of-the-box metrics included in an integration, such as the metric name, type, interval, and unit.
- More information about
metadata.csv fields can be found in the Integrations Assets Reference.
- Note: All Marketplace metrics count as custom metrics.
Dashboards and monitors
- Contain the out-of-the-box dashboards and monitors (alerts) for your integration.
- You can create dashboards and monitors directly in your sandbox account and export them as JSON files.
- See Dashboarding Best Practices for details.
- Consists of at least one SVG, which the Datadog DesignOps team implements throughout the Datadog site for both light and dark modes. Logo SVG files can be added to the
assets directory, or you can place them in a
logos sub-directory under
- Note: Technology Partners are responsible for the licensing of the logos they submit.
- Captures release notes and version information, and displays this in the “Release Notes” tab of your tile. Add release notes in descending order (latest version at the top).
- Lives in the shared
.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.
Additional Marketplace files
- The Technology Partner’s own End User License Agreement (EULA) is required for all Marketplace offerings.
Submit a pull request
Submit a pull request containing your integration assets 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.
Approve tile for release
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 the integration tile in the Datadog Marketplace and make changes before it goes live.
Coordinate go-to-market opportunities
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:
- A Datadog quote for partner press releases
- A Blog Post in the Datadog Monitor
- Amplification of social media posts
Email email@example.com if you have any questions.
Additional helpful documentation, links, and articles: