Update SCA onboarding requirements and clarify APM usage - #38498
Open
ayela232 wants to merge 1 commit into
Open
Conversation
Clarified requirements for Software Composition Analysis, emphasizing that only the Datadog Agent and SDK are necessary, while APM and Infrastructure Monitoring are optional. Also added context on APM costs.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the runtime Software Composition Analysis (SCA) setup documentation to clarify required vs. optional Datadog components, aiming to reduce onboarding friction and set expectations around APM usage/costs.
Changes:
- Removes “Datadog APM Configuration” as a prerequisite for runtime SCA setup.
- Adds an informational note stating that only the Datadog Agent and supported SDK are required, and that APM/Infrastructure Monitoring are optional.
- Adds brief cost-related context when APM tracing is disabled (but still needed for certain SCA-related telemetry).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 3. **Supported SDK:** The Datadog SDK used by your application or service supports Software Composition Analysis capabilities for the language of your application or service. For more details, refer to the [Library Compatibility][2] page. | ||
| 2. **Supported SDK:** The Datadog SDK used by your application or service supports Software Composition Analysis capabilities for the language of your application or service. For more details, refer to the [Library Compatibility][2] page. | ||
|
|
||
| <div class="alert alert-info">The Datadog Agent and SDK are the only requirements for SCA. APM tracing and Infrastructure Monitoring are not required; SCA reports findings independently of both. To disable APM or Infrastructure Monitoring, see <a href="#disable-apm-and-infrastructure-monitoring">Disable APM and Infrastructure Monitoring</a>. If APM is disabled, expect some APM intake costs to support SCA features (for example, security traces and spans).</div> |
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
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.
Clarified requirements for Software Composition Analysis, emphasizing that only the Datadog Agent and SDK are necessary, while APM and Infrastructure Monitoring are optional. Also added context on APM costs.
What does this PR do? What is the motivation?
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes