[kafka] Surface Kafka Monitoring above the fold in the integration README#23710
Merged
Conversation
Surfaces /data_streams/kafka above-the-fold for readers landing on the Kafka integration tile / docs page. UTM params on the link (utm_campaign=DocsCTA-DSMKafka-IntegrationsKafka) let us attribute click-through from this specific page in web analytics. This is one of five high-traffic Kafka pages getting the same treatment; campaign rollup is DSMKafka. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
README files are plain markdown and don't render Hugo shortcodes (used in the sibling docs PR for a boxed callout). Switching to a clean bold lead-in here so the visual treatment is consistent with other README "tip"-style callouts and doesn't look like a quote block. UTM tracking unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Switches the top callout to the same purple "NEW Kafka Monitoring" box treatment used in the sibling docs PR, with Piotr's wording (consumer lag, throughput, schemas, message reading). Removes two redundant mid-page "Add Data Streams Monitoring..." lines that duplicated the top callout. Cleans up the now-orphan [24] and [25] reference definitions. Per @piochelepiotr's PR comment. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The custom purple HTML box stood out against the rest of the README's clean markdown. Replaced with a single-line bold lead-in that matches the file's existing style. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Validation ReportAll 20 validations passed. Show details
|
johannbotha
changed the title
piochelepiotr
approved these changes
May 18, 2026
joepeeples
approved these changes
May 18, 2026
temporal-github-worker-1
Bot
added
docs/approved
and removed
docs/review-requested
labels
pull Bot
pushed a commit
to ConnectionMaster/integrations-core
that referenced
this pull request
May 19, 2026
…3751) /data_streams/kafka (no trailing slash) returns a 302 to /data_streams/kafka/ that strips the query string, so the UTM tracking on the callout link added in DataDog#23710 was being silently dropped before it reached RUM. Verified: curl -I /data_streams/kafka?utm_campaign=X -> 302 (UTM lost) curl -I /data_streams/kafka/?utm_campaign=X -> 200 (UTM preserved) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
labbati
reviewed
May 26, 2026
|
|
||
| The Agent's Kafka check is included in the [Datadog Agent][4] package, no additional installation is needed on your Kafka nodes. | ||
|
|
||
| Add [Data Streams Monitoring][24] to your producers and consumers to visualize the application topology, root cause issues across services, and measure end to end latency, throughput and lag. |
Member
There was a problem hiding this comment.
What's the rationale for removing all classic DSM links? Save real estate?
Contributor
Author
There was a problem hiding this comment.
IMO having multiple callouts to DSM will reduce the efficacy of either callout. The callout that is most applicable here is the callout to kafka monitoring so I decided to make that one more prominent .
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
4 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.
What does this PR do?
Adds a single bold "New:" callout immediately under the dashboard image on the Kafka integration README, linking readers to
/data_streams/kafka(the new Kafka Monitoring page on docs.datadoghq.com).Also consolidates: removes two redundant mid-page lines that already mentioned Data Streams Monitoring (in Overview and Installation sections), and drops two now-orphan reference definitions (
[24],[25]).Motivation
The Kafka integration page is one of the top Datadog pages returned by Google for "kafka datadog". Surfacing the new Kafka Monitoring capability above the fold (instead of buried mid-page) gives readers landing from search a direct path to the new feature.
Wording is per @piochelepiotr's PR-review suggestion — concrete capabilities (consumer lag, throughput, schemas, message reading) instead of a generic "lag/throughput/lineage" pitch.
Links
Tracking
UTM params on the destination link (
utm_campaign=DocsCTA-DSMKafka-IntegrationsKafka) so click-through from this page is attributable in web analytics. SharedDSMKafkacampaign rollup with the sibling PRs on documentation and corp-hugo.Review checklist (to be filled by reviewers)
README-only change; tests N/A. Suggest applying `qa/skip-qa`.
AI assistance
Drafted with Claude Code (Claude Opus 4.7); wording, placement, and consolidation reviewed by the author and refined per @piochelepiotr's feedback.
Related PRs
Sibling PRs adding equivalent callouts to other high-traffic Kafka surfaces: