From 24890385bebc8cc83e3ecfa17c148de52ba5a57b Mon Sep 17 00:00:00 2001 From: JJ Botha Date: Thu, 14 May 2026 13:24:57 -0400 Subject: [PATCH 1/4] [kafka] Add Data Streams Monitoring callout above the fold 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) --- kafka/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kafka/README.md b/kafka/README.md index 90c6c341d6901..7258a7c285864 100644 --- a/kafka/README.md +++ b/kafka/README.md @@ -2,6 +2,8 @@ ![Kafka Dashboard][1] +*Already collecting Kafka metrics with the Agent? **[Data Streams Monitoring for Kafka][26]** layers end-to-end lag, throughput, and message lineage across your producers and consumers.* + ## Overview View Kafka broker metrics and logs for a 360-view of the health and performance of your Kafka clusters in real time. @@ -186,3 +188,4 @@ See [service_checks.json][15] for a list of service checks provided by this inte [23]: https://www.datadoghq.com/knowledge-center/apache-kafka/ [24]: https://docs.datadoghq.com/data_streams/ [25]: /data-streams +[26]: https://docs.datadoghq.com/data_streams/kafka?utm_source=docs&utm_medium=callout&utm_campaign=DocsCTA-DSMKafka-IntegrationsKafka From 024de48fae77059e71885dae71f1f7a6bcc605ad Mon Sep 17 00:00:00 2001 From: JJ Botha Date: Thu, 14 May 2026 14:09:55 -0400 Subject: [PATCH 2/4] Drop italic block on Kafka README callout 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) --- kafka/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kafka/README.md b/kafka/README.md index 7258a7c285864..dab5f91f22e38 100644 --- a/kafka/README.md +++ b/kafka/README.md @@ -2,7 +2,7 @@ ![Kafka Dashboard][1] -*Already collecting Kafka metrics with the Agent? **[Data Streams Monitoring for Kafka][26]** layers end-to-end lag, throughput, and message lineage across your producers and consumers.* +**Already collecting Kafka metrics with the Agent?** Pair them with [Data Streams Monitoring for Kafka][26] to track end-to-end producer/consumer lag, throughput, and message lineage. ## Overview From d4e3dbec1c7626d35e505a2efb4ce844425b26f1 Mon Sep 17 00:00:00 2001 From: JJ Botha Date: Mon, 18 May 2026 13:39:59 -0400 Subject: [PATCH 3/4] [kafka] Consolidate DSM mentions into a single top-of-page callout 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) --- kafka/README.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/kafka/README.md b/kafka/README.md index dab5f91f22e38..70286d2b06934 100644 --- a/kafka/README.md +++ b/kafka/README.md @@ -2,14 +2,17 @@ ![Kafka Dashboard][1] -**Already collecting Kafka metrics with the Agent?** Pair them with [Data Streams Monitoring for Kafka][26] to track end-to-end producer/consumer lag, throughput, and message lineage. +
+

+ New + Kafka Monitoring tracks consumer lag, throughput, schemas, and adds message reading capabilities. Try Kafka Monitoring → +

+
## Overview View Kafka broker metrics and logs for a 360-view of the health and performance of your Kafka clusters in real time. -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. - **Note**: - This check has a limit of 350 metrics per instance. The number of returned metrics is indicated in the Agent status output. Specify the metrics you are interested in by editing the configuration below. For more detailed instructions on customizing the metrics to collect, see the @@ -27,8 +30,6 @@ To collect Kafka consumer metrics, see the [kafka_consumer check][3]. 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. - The check collects metrics from JMX with [JMXFetch][5]. A JVM is needed on each kafka node so the Agent can run JMXFetch. The same JVM that Kafka uses can be used for this. **Note**: The Kafka check cannot be used with Managed Streaming for Apache Kafka (Amazon MSK). Use the [Amazon MSK integration][6] instead. @@ -186,6 +187,3 @@ See [service_checks.json][15] for a list of service checks provided by this inte [21]: https://www.datadoghq.com/blog/monitor-kafka-with-datadog [22]: https://raw.githubusercontent.com/DataDog/dd-agent/5.2.1/conf.d/kafka.yaml.example [23]: https://www.datadoghq.com/knowledge-center/apache-kafka/ -[24]: https://docs.datadoghq.com/data_streams/ -[25]: /data-streams -[26]: https://docs.datadoghq.com/data_streams/kafka?utm_source=docs&utm_medium=callout&utm_campaign=DocsCTA-DSMKafka-IntegrationsKafka From fbcd27856c337b78d1670a77a0a1b2cc6a2f3621 Mon Sep 17 00:00:00 2001 From: JJ Botha Date: Mon, 18 May 2026 13:44:41 -0400 Subject: [PATCH 4/4] Drop inline HTML; use plain markdown for Kafka Monitoring callout 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) --- kafka/README.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/kafka/README.md b/kafka/README.md index 70286d2b06934..cb5959f23f287 100644 --- a/kafka/README.md +++ b/kafka/README.md @@ -2,12 +2,7 @@ ![Kafka Dashboard][1] -
-

- New - Kafka Monitoring tracks consumer lag, throughput, schemas, and adds message reading capabilities. Try Kafka Monitoring → -

-
+**New:** [Kafka Monitoring][24] tracks consumer lag, throughput, schemas, and adds message reading capabilities. ## Overview @@ -187,3 +182,4 @@ See [service_checks.json][15] for a list of service checks provided by this inte [21]: https://www.datadoghq.com/blog/monitor-kafka-with-datadog [22]: https://raw.githubusercontent.com/DataDog/dd-agent/5.2.1/conf.d/kafka.yaml.example [23]: https://www.datadoghq.com/knowledge-center/apache-kafka/ +[24]: https://docs.datadoghq.com/data_streams/kafka?utm_source=docs&utm_medium=callout&utm_campaign=DocsCTA-DSMKafka-IntegrationsKafka