add Developer Platform instructions #32481
Open
+156
−183
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Preview links (active after the
|
eho1307
requested changes
Nov 3, 2025
evazorro
requested changes
Nov 3, 2025
Contributor
evazorro
left a comment
evazorro
left a comment
There was a problem hiding this comment.
A few fixes and a note/question about formatting on some of the procedures. I'd love to take another look before merge.
Co-authored-by: Erica Ho <109224841+eho1307@users.noreply.github.com>
Co-authored-by: Erica Ho <109224841+eho1307@users.noreply.github.com>
eho1307
reviewed
Nov 6, 2025
nubtron
requested changes
Nov 7, 2025
| Ensure following tools are installed: | ||
|
|
||
| ## Prerequisites | ||
| - Python v3.12 |
Contributor
There was a problem hiding this comment.
We're using Python 3.13 now - perhaps we could remove this step here since it's part of the ddev steps anyway?
| The following example shows logic for an integration named `Awesome`. | ||
|
|
||
| For Awesome, the Agent Check is composed of a [service check][25] named `awesome.search` that searches for a string on a web page. It results in `OK` if the string is present, `WARNING` if the page is accessible but the string was not found, and `CRITICAL` if the page is inaccessible. | ||
| This check defines a [service check][4] called `awesome.search`, which searches a webpage for a specific string: |
Contributor
There was a problem hiding this comment.
(non-blocker) I'll make an issue to remove service checks from examples in general, we want to move away from them because metrics are better for the same purpose.
|
|
||
| <div class="alert alert-info">If you are creating an integration for the Datadog Marketplace, ensure that your directory follows the pattern of {partner name}_{integration name}.</div> | ||
| ```shell | ||
| ddev create -t check_only <YOUR_INTEGRATION_NAME> --skip-manifest |
Contributor
There was a problem hiding this comment.
What's the reason behind using check_only?
eho1307
approved these changes
Nov 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Add Developer Platform instructions for Agent-based integrations