[reorg fix] Update RUM ownership of views page with rules - #38887
Closed
jhgilbert wants to merge 36 commits into
Closed
[reorg fix] Update RUM ownership of views page with rules#38887jhgilbert wants to merge 36 commits into
jhgilbert wants to merge 36 commits into
Conversation
jhgilbert
added
WORK IN PROGRESS
1 task
This comment has been minimized.
This comment has been minimized.
* (maint) Post-migration cleanup script * Remove extraneaous file
Staged file paths include a leading hugo/ segment, so parts[2] pointed at "en" instead of the actual top-level section name. Use parts[3].
* Update labeler paths * Update labeler paths
…ith Terraform (#38865) * Add guide for managing Incident Management with Terraform Adds a new guide covering incident types, custom fields, responder roles, notification templates/rules, and postmortem templates using the Datadog Terraform provider, and links it from the guides index. * Rewrite Incident Management Terraform guide as a loose guide Simplify to a short guide with links to the Terraform registry and existing docs per PM feedback, instead of duplicating per-resource code examples. * Align Terraform guide sections with UI naming and add Information settings coverage Rename sections to match the Settings UI labels (Property Fields, Responder Types), reorder to match the UI sidebar, and cross-link Information page settings (private incidents, incident deletion, severity/status) to the Terraform resources that configure them. * Fix alignment in Terraform notification rule example * Apply suggestion from @rtrieu Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com> * Apply suggestion from @estherk15 --------- Co-authored-by: Esther Kim <esther.kim@datadoghq.com> Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
…umentation CRD (#37532) * Document configuring Autodiscovery with the DatadogInstrumentation CRD Add a new guide describing how to configure Autodiscovery checks for Kubernetes workloads through the DatadogInstrumentation custom resource (beta) instead of pod annotations, and cross-reference it from the existing Autodiscovery pages. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Document DatadogInstrumentation Autodiscovery usage * chore: improve some wording * chore: ddi guide improvements * chore: improve prometheus, logs and endpointchecks pages * Refine DatadogInstrumentation guide and Prometheus pointer - Use present tense for precedence and validation behavior - Add "Verify scheduled checks" section with an agent configcheck example - Remove the redundant status section - Point Prometheus Operator users to the DDI CRD as the PodMonitor/ServiceMonitor equivalent - Fix a trailing space in the Prometheus DDI example Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Add DatadogInstrumentation tab to Prometheus OpenMetrics example Show the OpenMetrics check as a DatadogInstrumentation resource alongside the annotation examples, note the 7.81+ requirement, and call out removing the annotation from the example manifest so the resource takes effect. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Clarify DatadogInstrumentation autodiscovery docs * chore: reword verify scheduled checks section * chore: revert all kubernetes log page changes * Update DatadogInstrumentation docs for logs support * docs: add back logs section change * improve wording and structure of DDI crd docs * Move DatadogInstrumentation CRD tab into Autodiscovery configuration * Document DatadogInstrumentation configuration and logging * Update DatadogInstrumentation CRD setup requirements * chore: remove unused initConfig if not relevant * chore(refactor): clean up wording for DDI * chore(refactor): Improve logs and prometheus changes * chore(refactor): address comments --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
* Fix minimum Datadog Agent version for Python ddtrace v4 Update the minimum Datadog Agent version for the >=4.0,<5 release branch from 7.28 to 7.63.0 to match the v4 migration guide requirement. Co-authored-by: Cursor <cursoragent@cursor.com> * Fix typo: Maintenence -> Maintenance Co-authored-by: Cursor <cursoragent@cursor.com> * Clarify Trace Agent 7.76.1 as recommended, not required The 7.76.1 figure is a recommendation tied to auth parameter obfuscation, not a hard minimum requirement to run the tracer. Co-authored-by: Cursor <cursoragent@cursor.com> * Revert "Clarify Trace Agent 7.76.1 as recommended, not required" This reverts commit 1820333. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
…e Rationale) (#38001) * Correct custom rule message formatting docs (remove References, demote Rationale) The previously documented References section is not rendered in the finding panel (the parsed references section has no consumer in the frontend), so remove it. Demote Rationale from a placement row to a note: it renders within What Happened after the description, without its own labeled section. Follow-up correction to #37983. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Drop "without its own labeled section" from Rationale note Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Added note about APM intake costs even when APM is disabled. Co-authored-by: ayela232 <anil.yelamarty@datadoghq.com> Co-authored-by: May Lee <may.lee@datadoghq.com>
* Fix preview_links.py paths broken by the hugo/ repo reorg Points the mako template load at hugo/local/bin/py/, and updates the content/en/ path matching to also accept the hugo/ prefix so preview links resolve for files under the post-reorg layout. * Tweak solution --------- Co-authored-by: zeina.gebran <zeina.gebran@datadoghq.com>
Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>
* Add Data Observability integration overhead page Document the compute overhead of Data Observability and how to control it: - Quality Monitoring: how each metric is collected per warehouse (Snowflake reads INFORMATION_SCHEMA metadata for row count/freshness; BigQuery uses the table metadata API; Databricks queries the SQL warehouse for every metric), what drives the cost, and how to reduce it. - Jobs Monitoring: the Datadog Agent's footprint on Spark/Databricks clusters (in-process Spark listener, no warehouse queries; none on serverless), and how to reduce it. Adds a top-level "Integration Overhead" nav entry under Data Observability. Modeled on the Database Monitoring agent integration overhead page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Address Vale findings: split long sentences, replace spaced dashes, fix list comma Keep product metric names (Percent Zero/Percent Negative) and the Quality Monitoring product name in the heading; the remaining Vale notices on those are false positives on proper nouns. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Address remaining Vale nits: drop 'very', shorten Notes sentence Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Correct Jobs Monitoring footprint: span volume tracks stages/jobs, not tasks The Spark listener emits spans per application/job/stage/SQL-execution/ streaming-batch, plus one span per *failed* task; successful tasks are aggregated into stage metrics and emit no spans (per-task executor tracing is disabled in DJM). Trace volume therefore scales with job structure, not task count or data volume, and trace throughput is low. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Scope row-count scan cost to Databricks (address Codex review) Row count grows with table size only on Databricks (COUNT scan); on Snowflake and BigQuery it is a metadata read. Column-statistic queries scan data on every warehouse. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Add OpenLineage-based integrations to Jobs Monitoring overhead Document the second JM delivery path: Airflow, dbt, and custom pipelines emit OpenLineage events from an open-source integration the customer runs (not the Datadog Agent). Overhead is in-process, proportional to runs/tasks and metadata, not data volume; reference OpenLineage + Airflow provider OS docs (and the Spark circuit breaker for direct-OpenLineage Spark). Add a two-path framing at the top of the section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Vale: use 'open source', split Notes sentence Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Correct dbt monitoring overhead: follows structured logs, no perf impact dbt Core uses dbt-ol --consume-structured-logs to follow dbt's structured logs and emit events as the run progresses (not a post-run parse), so it does not affect dbt performance; dbt Cloud uses webhooks. Soften the intro's in-process generalization, which doesn't hold for those paths. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Address review (aboitreaud): drop driver-only install + Spark-direct-OpenLineage detour - Agent runs on the driver and executors (not 'optionally the workers'); there is no driver-only install method, so remove that tuning bullet. - Remove the 'instrument Spark directly with OpenLineage' suggestion and the Spark circuit-breaker reference (steered off the supported Agent-based path). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * small edits * Remove stray diff.renameLimit override in check-section-index.py --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: cswatt <cecilia.watt@datadoghq.com> Co-authored-by: Adrien Boitreaud <adrien.boitreaud@datadoghq.com> Co-authored-by: Adrien Boitreaud <72934368+aboitreaud@users.noreply.github.com>
Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>
* Update grok_parser.md * Add files via upload * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * add in-line govsite callout * Update content/en/logs/log_configuration/processors/grok_parser.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update content/en/logs/log_configuration/processors/grok_parser.md Co-authored-by: Esther Kim <esther.kim@datadoghq.com> * Update grok_parser.md --------- Co-authored-by: njung009 <nicolas.jung@datadoghq.com> Co-authored-by: Max Phillips <maxvphillips@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Max Phillips <max.phillips@datadoghq.com> Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
* Document Entra roles attribute setup * Link Entra role attribute instructions
* Update Kafka demo with connectors * Collect Kafka Connect integration data
* Document creating RUM operations from Datadog * Updated instructions and added image * Updated Browser SDK APIs to remove experimental opt-in * Updated minor details * Fix typos in operations creation instructions * Apply suggestions from code review Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com> --------- Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>
* Document 7-day SDS example log retention for gov sites Adds gov-only documentation for the SDS example finding log retention change from 3 to 7 days: a new row on the data retention periods page, and updated wording in the Investigate Sensitive Data Findings guide. Commercial sites are unchanged and continue to reference the 3-day retention period. * Update data_retention_periods.md * Update hugo/content/en/security/sensitive_data_scanner/guide/investigate_sensitive_data_findings.md Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com> * Update hugo/content/en/data_security/data_retention_periods.md Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com> --------- Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com>
* ad note * small edit
* Remove Agent config template build dependency * Remove redundant Agent configuration example
* Document coverage report merging and partial coverage Add a Code Coverage Calculation page explaining that Datadog merges all reports for a repo/commit pair, how overlapping files are combined, and how partially covered lines are counted. Add the nav entry and cross-links from the index, setup, and flags pages. Environment: Datadog workspace Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Shorten long sentences flagged by Vale Vale's sentencelength rule flagged five sentences over 25 words on the new Coverage Calculation page. Split them; the page now reports no Vale alerts. Environment: Datadog workspace Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Apply suggestions from code review Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com>
The Edit button pointed to content/<lang>/<path>, but content now lives under hugo/content/ following the recent migration. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
…am (#39018) * Document default Session Replay retention via account team * Move default-retention note next to the 30-day default statement
…ocs (#39019) * Add Node.js image_parts annotation example to LLM Observability SDK docs Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Clarify that imageParts are not yet auto-captured Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
…38844) * Clarify auto multi-line before/after example in Overview The Overview example rendered identically before and after aggregation, so the effect of the feature was not visible, and the surrounding text stated the stack trace was aggregated into "a single log" when the example actually produces two. - Annotate each line in the "before" block to show the Agent emits one log per line when detection is disabled. - Bracket the aggregated lines in the "after" block and label the two resulting logs, so the grouping is legible in rendered output. - Explain that only lines beginning with a datetime start a new log, which is why the trailing INFO line remains its own log. - Use `text` fences and add blank lines around them, matching the convention used in the custom samples section. Co-Authored-By: Claude <noreply@anthropic.com> * Fix formatting of auto multi-line detection logs Updated the formatting of log examples for clarity. * Fix formatting in auto_multiline_detection.md * Revise log examples for Auto multi-line detection Updated examples to illustrate the effect of Auto multi-line detection on log formatting. * Fix grammar in auto multi-line detection documentation Corrected a minor grammatical error in the explanation of auto multi-line detection. * Fix formatting and capitalization in auto multi-line detection doc Corrected capitalization and formatting inconsistencies in the documentation regarding auto multi-line detection. * Update hugo/content/en/agent/logs/auto_multiline_detection.md Co-authored-by: Eva Parish <eva.parish@datadoghq.com> * Modify log example for clarity on multi-line detection Updated example log output to reflect auto multi-line detection. * Update explanation of auto multi-line detection Clarified how auto multi-line detection aggregates logs. * Update description of auto multi-line detection Clarified the default behavior of auto multi-line detection regarding log entries. --------- Co-authored-by: ralph.hyacinthe <ralph.hyacinthe@datadoghq.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Eva Parish <eva.parish@datadoghq.com>
* Document Codex config.toml header for MCP toolsets * Note Codex CLI header requirement for MCP toolsets * Apply suggestions from code review Co-authored-by: Eva Parish <eva.parish@datadoghq.com> --------- Co-authored-by: Eva Parish <eva.parish@datadoghq.com>
Updated preferred Datadog Agent version and noted bug in v7.82.0.
Co-authored-by: raphael.desboscs <raphael.desboscs@datadoghq.com> Co-authored-by: rphdbddog <296187607+rphdbddog@users.noreply.github.com>
… into reorg-fix/pr-38673
github-actions
Bot
added
Architecture
Contributor
Contributor
|
1 task
Contributor
|
Closing in favor of #39065, which contains only Arti's original two commits without the extra commits that had accumulated from master. |
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
19 participants
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.
🤖 Auto-generated fix for #38673.
@arti-arutiunov — the docs repo reorg created merge conflicts in your PR #38673. This is an auto-generated replacement with the file paths fixed; please use it instead of the original.
This PR replays the commits from #38673 with file paths translated to the post-reorg
hugo/layout. The original commits are preserved — same messages and authorship.The original PR (#38673) will be closed in favor of this one.
Next steps:
WORK IN PROGRESSlabel from this PR.Original PR description:
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