Update instructions with Datadog Agent source and Cloudprem dest #33314
+34
−19
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
estherk15
commented
Dec 11, 2025
| 1. Select the [**Datadog CloudPrem** destination][4] to forward logs to your CloudPrem instance. Leave the configuration empty. | ||
|
|
||
| {{< img src="/cloudprem/ingest/observability-pipelines-cloudprem-setup.png" alt="Screenshot of the Logs Explorer interface showing how to filter logs by selecting the cloudprem index in the facets panel" style="width:80%;" >}} | ||
| <!-- This image shows an example with dual shipping when the instructions say log volume control --> |
Contributor
Preview links (active after the
|
estherk15
commented
Dec 11, 2025
| --set datadog.apiKey=XXXXXXX \ | ||
| --set datadog.pipelineId=XXXXXXX \ | ||
| --set env[0].name=DD_OP_SOURCE_HTTP_SERVER_ADDRESS,env[0].value='0.0.0.0:8282' \ | ||
| --set env[1].name=DD_OP_DESTINATION_HTTP_CLIENT_URI,env[1].value='http://<RELEASE_NAME>-indexer.<NAMESPACE_NAME>.svc.cluster.local:7280/api/v2/datadog' \ |
Contributor
Author
There was a problem hiding this comment.
I wasn't sure if this needs to be removed or not? The CloudPrem destination docs state that
The Worker appends /api/v2/logs and /api/v1/validate to the endpoint URL, so these endpoints must be allowed if you are using forwarding or firewall rules.
cswatt
approved these changes
Dec 11, 2025
Contributor
cswatt
left a comment
cswatt
left a comment
There was a problem hiding this comment.
This mostly LGTM so I'm approving for now, but noting that there's ongoing conversations open
estherk15
commented
Jan 7, 2026
|
|
||
| {{< img src="/cloudprem/ingest/observability-pipelines-cloudprem-setup.png" alt="Screenshot of the Logs Explorer interface showing how to filter logs by selecting the cloudprem index in the facets panel" style="width:80%;" >}} | ||
| <!-- This image shows an example with dual shipping when the instructions say log volume control --> | ||
| <!-- {{< img src="/cloudprem/ingest/observability-pipelines-cloudprem-setup.png" alt="Screenshot of the Logs Explorer interface showing how to filter logs by selecting the cloudprem index in the facets panel" style="width:80%;" >}} --> |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| <!-- {{< img src="/cloudprem/ingest/observability-pipelines-cloudprem-setup.png" alt="Screenshot of the Logs Explorer interface showing how to filter logs by selecting the cloudprem index in the facets panel" style="width:80%;" >}} --> |
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?
Merge instructions
Merge readiness: