Update Kafka OOTB dashboards' Data Streams setup doc link

[piochelepiotr]

Summary

• Updates the Data Streams Monitoring setup documentation link in both Kafka OOTB dashboards (kafka_dashboard.json and kafka_kraft_dashboard.json) from the old data_streams/setup/technologies/kafka referrer URL to https://docs.datadoghq.com/data_streams/kafka/setup/.

Test plan

• Validate dashboard JSON via ddev meta dash export/schema validation in CI
• Confirm new link resolves correctly on docs site
• Visually confirm "Useful Links" and "Learn More" sections render correctly in staging

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   1 (always emitted)
Diff (2 files):
  kafka/assets/dashboards/kafka_dashboard.json
  kafka/assets/dashboards/kafka_kraft_dashboard.json

Debug a specific task: evalya plan impact --path <path> --task <task>

Learn more about CI impact filtering

[datadog-official]

⚠️ Warnings

🚦 1 Pipeline job failed

Validate repository | Run Validations / Validate

View in Datadog · View in GitHub Actions

PR #24919 is missing an Agent-release QA decision label. Every pull request must declare whether its changes require QA validation.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 6dfe6b3 | Docs | View more details | Give us feedback!}

[dd-octo-sts]

Validation Report

Validation	Description	Status
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	❌

Run ddev validate all changed --fix to attempt to auto-fix supported validations.

Passed validations (20)

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run