Skip to content

Add blog links to further_reading (week of 2026-08-21) - #39390

Draft
dd-octo-sts[bot] wants to merge 2 commits into
masterfrom
blog-linker/weekly-2026-08-21
Draft

Add blog links to further_reading (week of 2026-08-21)#39390
dd-octo-sts[bot] wants to merge 2 commits into
masterfrom
blog-linker/weekly-2026-08-21

Conversation

@dd-octo-sts

@dd-octo-sts dd-octo-sts Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Adds Datadog blog post links to the further_reading section of the docs pages
those posts reference. Opened automatically by the blog linker workflow;
covers posts from the last 14 days.

Script output

SUMMARY
==================================================

Blog links reviewed:
- https://www.datadoghq.com/blog/how-to-manage-unfixed-kubernetes-cves (2026-08-10)
- https://www.datadoghq.com/blog/serverless-agentic-onboarding (2026-08-10)
- https://www.datadoghq.com/blog/engineering/improving-apm-java-startup-with-a-prefix-trie (2026-08-11)
- https://www.datadoghq.com/blog/product-analytics-account-segments (2026-08-11)
- https://www.datadoghq.com/blog/azure-secretless-authentication (2026-08-12)
- https://www.datadoghq.com/blog/data-pipeline-monitoring (2026-08-14)
- https://www.datadoghq.com/blog/two-ways-to-measure-cumulative-impact (2026-08-18)
- https://www.datadoghq.com/blog/work-management (2026-08-18)
- https://www.datadoghq.com/blog/trace-aws-lambda-durable-functions (2026-08-18)
- https://www.datadoghq.com/blog/cisa-bod-26-04-vulnerability-prioritization (2026-08-19)
- https://www.datadoghq.com/blog/engineering/gitretriever (2026-08-19)
- https://www.datadoghq.com/blog/ai-native-sast-detect-llm-vulnerabilities (2026-08-20)
- https://www.datadoghq.com/blog/systemic-risk-ai-agents-datadog (2026-08-20)

Documents updated:
- /security/cloud_siem
- /mcp_server
- /serverless
- /continuous_integration
- /tracing
- /tracing/live_debugger
- /account_management/rbac/permissions
- /product_analytics/profiles
- /real_user_monitoring
- /session_replay
- /data_observability
- /data_streams
- /database_monitoring
- /logs
- /real_user_monitoring
- /security/cloud_siem
- /serverless
- /synthetics
- /tracing
- /experiments/concepts/cumulative_impact
- /experiments/statistics/analysis_methods
- /actions/agents
- /actions/workflows
- /bits_ai/bits_chat
- /error_tracking
- /incident_response/incident_management/investigate/declare
- /incident_response/work_management
- /incident_response/work_management/automation_rules
- /incident_response/work_management/create_work_item
- /incident_response/work_management/notifications_integrations
- /incident_response/work_management/view_and_manage
- /mcp_server/tools
- /monitors
- /security/cloud_siem
- /security/ticketing_integrations
- /serverless/aws_lambda/durable_functions
- /serverless/aws_lambda/instrumentation/nodejs
- /tracing/trace_pipeline/trace_retention
- /security/cloud_security_management
- /security/cloud_security_management/crown_jewels
- /security/cloud_security_management/triage_and_prioritize/runtime_prioritization_engine
- /security/mcp_server
- /tracing/glossary
- /pr_gates
- /security/code_security
- /security/code_security/dev_tool_int/pull_request_comments
- /security/code_security/static_analysis/ai_enhanced_sast
- /actions/workflows
- /incident_response/work_management
- /llm_observability

Documents unable to update:
- /security/default_rules/wpm-g1s-8yx (skipped:not-found)
- /real_user_monitoring/application_monitoring/browser/advanced_configuration (skipped:not-found)

Skipped:
- /integrations/azure (integration-doc)
- /integrations/airbyte (integration-doc)
- /integrations/airflow (integration-doc)
- /integrations/amazon-kafka (integration-doc)
- /integrations/amazon-kinesis (integration-doc)
- /integrations/amazon-s3 (integration-doc)
- /integrations/confluent-cloud (integration-doc)
- /integrations/dagster-plus (integration-doc)
- /integrations/databricks (integration-doc)
- /integrations/dbt-cloud (integration-doc)
- /integrations/flink (integration-doc)
- /integrations/google-cloud-bigquery (integration-doc)
- /integrations/google-cloud-storage (integration-doc)
- /integrations/kafka (integration-doc)
- /integrations/kafka-consumer (integration-doc)
- /integrations/snowflake-web (integration-doc)
- /integrations/jira (integration-doc)
- /integrations/linear (integration-doc)
- /integrations/servicenow (integration-doc)


DETAILS
==================================================

1. https://www.datadoghq.com/blog/how-to-manage-unfixed-kubernetes-cves (2026-08-10)
   documents updated:
      /security/cloud_siem
   documents unable to update:
      /security/default_rules/wpm-g1s-8yx (skipped:not-found)

2. https://www.datadoghq.com/blog/serverless-agentic-onboarding (2026-08-10)
   documents updated:
      /mcp_server
      /serverless

3. https://www.datadoghq.com/blog/engineering/improving-apm-java-startup-with-a-prefix-trie (2026-08-11)
   documents updated:
      /continuous_integration
      /tracing
      /tracing/live_debugger

4. https://www.datadoghq.com/blog/product-analytics-account-segments (2026-08-11)
   documents updated:
      /account_management/rbac/permissions
      /product_analytics/profiles
      /real_user_monitoring
      /session_replay
   documents unable to update:
      /real_user_monitoring/application_monitoring/browser/advanced_configuration (skipped:not-found)

5. https://www.datadoghq.com/blog/azure-secretless-authentication (2026-08-12)
   skipped:
      /integrations/azure (integration-doc)

6. https://www.datadoghq.com/blog/data-pipeline-monitoring (2026-08-14)
   documents updated:
      /data_observability
      /data_streams
      /database_monitoring
      /logs
      /real_user_monitoring
      /security/cloud_siem
      /serverless
      /synthetics
      /tracing
   skipped:
      /integrations/airbyte (integration-doc)
      /integrations/airflow (integration-doc)
      /integrations/amazon-kafka (integration-doc)
      /integrations/amazon-kinesis (integration-doc)
      /integrations/amazon-s3 (integration-doc)
      /integrations/confluent-cloud (integration-doc)
      /integrations/dagster-plus (integration-doc)
      /integrations/databricks (integration-doc)
      /integrations/dbt-cloud (integration-doc)
      /integrations/flink (integration-doc)
      /integrations/google-cloud-bigquery (integration-doc)
      /integrations/google-cloud-storage (integration-doc)
      /integrations/kafka (integration-doc)
      /integrations/kafka-consumer (integration-doc)
      /integrations/snowflake-web (integration-doc)

7. https://www.datadoghq.com/blog/two-ways-to-measure-cumulative-impact (2026-08-18)
   documents updated:
      /experiments/concepts/cumulative_impact
      /experiments/statistics/analysis_methods

8. https://www.datadoghq.com/blog/work-management (2026-08-18)
   documents updated:
      /actions/agents
      /actions/workflows
      /bits_ai/bits_chat
      /error_tracking
      /incident_response/incident_management/investigate/declare
      /incident_response/work_management
      /incident_response/work_management/automation_rules
      /incident_response/work_management/create_work_item
      /incident_response/work_management/notifications_integrations
      /incident_response/work_management/view_and_manage
      /mcp_server/tools
      /monitors
      /security/cloud_siem
      /security/ticketing_integrations
   skipped:
      /integrations/jira (integration-doc)
      /integrations/linear (integration-doc)
      /integrations/servicenow (integration-doc)

9. https://www.datadoghq.com/blog/trace-aws-lambda-durable-functions (2026-08-18)
   documents updated:
      /serverless/aws_lambda/durable_functions
      /serverless/aws_lambda/instrumentation/nodejs
      /tracing/trace_pipeline/trace_retention

10. https://www.datadoghq.com/blog/cisa-bod-26-04-vulnerability-prioritization (2026-08-19)
    documents updated:
       /security/cloud_security_management
       /security/cloud_security_management/crown_jewels
       /security/cloud_security_management/triage_and_prioritize/runtime_prioritization_engine
       /security/mcp_server
       /tracing/glossary

11. https://www.datadoghq.com/blog/engineering/gitretriever (2026-08-19)
    no docs links found in blog

12. https://www.datadoghq.com/blog/ai-native-sast-detect-llm-vulnerabilities (2026-08-20)
    documents updated:
       /pr_gates
       /security/code_security
       /security/code_security/dev_tool_int/pull_request_comments
       /security/code_security/static_analysis/ai_enhanced_sast

13. https://www.datadoghq.com/blog/systemic-risk-ai-agents-datadog (2026-08-20)
    documents updated:
       /actions/workflows
       /incident_response/work_management
       /llm_observability


==================================================
NEXT STEPS
==================================================

Files have been updated on your current branch.

To commit and push your changes:
  git add .
  git commit -m 'Add blog links to further_reading'
  git push

Then create a PR on GitHub.

Merge readiness

  • Ready for merge

Additional notes

Each entry pairs a blog post with a docs page that post links to.

@dd-octo-sts dd-octo-sts Bot added the WORK IN PROGRESS No review needed, it's a wip ;) label Aug 21, 2026
@dd-octo-sts
dd-octo-sts Bot requested a review from jeff-morgan-dd August 21, 2026 14:53
@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ Possible site support note detected

The following files have a site-region shortcode at the top of the page that mentions a feature being "not available" or "not supported":

  • hugo/content/en/security/cloud_security_management/_index.md

Are you trying to document site support for a product? If so, the site-region shortcode is not the recommended approach. See the Documenting site support guide for the preferred method.

Applied the per-post ranked affinity rubric by hand against this week's
blog-linker output: for each post, kept links only to pages whose subject
the post substantively advances, and dropped links to pages where the
post's connection was incidental (a passing mention, nav/footer boilerplate,
or a generic reference unrelated to the page's core topic).

@jeff-morgan-dd jeff-morgan-dd left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Manual affinity pass — 5 yellow flags out of 31 pairings the script added (reds were already removed in the previous commit).

Each flag is a suggested change that deletes the entry: accept to drop the link, dismiss to keep it. Accept-by-default is deliberate — peer review is the second net.

Judged from the script's own record in the PR description, not the diff. Several + lines here are pre-existing entries the re-sort relocated (the Kafka Learning Center course, dtdg.co/fe, state-of-serverless) — those aren't this week's links and weren't judged.

Rubric in one line: the most specific page whose subject the post advances is the best home; a broader page is rarely also a home; existing blog-link count raises the bar; zero homes is a correct answer.

Comment on lines +72 to +74
- link: "https://www.datadoghq.com/blog/data-pipeline-monitoring/"
tag: "Blog"
text: "Data pipeline monitoring 101: Tracking health and performance across the data stack"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Affinity: yellow — data pipeline monitoring isn't Cloud SIEM's subject, and this page already carries 21 blog links in further_reading. /data_observability is the specific home for this post. Accept this suggestion to drop the entry; dismiss it to keep.

Suggested change
- link: "https://www.datadoghq.com/blog/data-pipeline-monitoring/"
tag: "Blog"
text: "Data pipeline monitoring 101: Tracking health and performance across the data stack"

Comment on lines +75 to +77
- link: "https://www.datadoghq.com/blog/work-management/"
tag: "Blog"
text: "Centralize human and agentic work with Datadog Work Management"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Affinity: yellow/incident_response/work_management is the specific home for this post and already links it. On a landing page with 21 existing blog links, a broader second home doesn't clear the bar. Accept this suggestion to drop the entry; dismiss it to keep.

Suggested change
- link: "https://www.datadoghq.com/blog/work-management/"
tag: "Blog"
text: "Centralize human and agentic work with Datadog Work Management"

Comment on lines +26 to +28
- link: "https://www.datadoghq.com/blog/data-pipeline-monitoring/"
tag: "Blog"
text: "Data pipeline monitoring 101: Tracking health and performance across the data stack"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Affinity: yellow — the post fanned out to 9 pages; /data_observability and /data_streams are where a reader looking for pipeline monitoring lands. Serverless is adjacent, not a home. Accept this suggestion to drop the entry; dismiss it to keep.

Suggested change
- link: "https://www.datadoghq.com/blog/data-pipeline-monitoring/"
tag: "Blog"
text: "Data pipeline monitoring 101: Tracking health and performance across the data stack"

Comment on lines +32 to +34
- link: "https://www.datadoghq.com/blog/data-pipeline-monitoring/"
tag: "Blog"
text: "Data pipeline monitoring 101: Tracking health and performance across the data stack"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Affinity: yellow — same fan-out. APM and data pipelines are related, but the specific pages won this post, and this landing page already carries 8 blog links. Accept this suggestion to drop the entry; dismiss it to keep.

Suggested change
- link: "https://www.datadoghq.com/blog/data-pipeline-monitoring/"
tag: "Blog"
text: "Data pipeline monitoring 101: Tracking health and performance across the data stack"

Comment on lines +38 to +40
- link: "https://www.datadoghq.com/blog/work-management/"
tag: "Blog"
text: "Centralize human and agentic work with Datadog Work Management"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Affinity: yellow — Work Management's own section is the home for this post. The Monitors landing page is a broader neighbor with 7 existing blog links. Accept this suggestion to drop the entry; dismiss it to keep.

Suggested change
- link: "https://www.datadoghq.com/blog/work-management/"
tag: "Blog"
text: "Centralize human and agentic work with Datadog Work Management"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

WORK IN PROGRESS No review needed, it's a wip ;)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant