<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dynatrace Hub - Apache Kafka latest releases</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>A list of extensions from Apache Kafka</description><atom:link href="https://hub-manager.hub.central.dynatrace.com/api/v1/public-hub/feed/extensions/apache-kafka/" rel="self"/><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 10:26:05 +0000</lastBuildDate><item><title>Apache Kafka 3.1.2</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;h4&gt;🐛 Fixed in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Fixed issue where the new Infrastructure &amp;amp; Operations app screens would not load properly.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 19 Aug 2026 10:26:05 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 3.1.0</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;h3&gt;⚠️WARNING⚠️: Possible breaking changes and warnings - PLEASE READ before upgrading:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;This version requires a &lt;em&gt;minimum Dynatrace version&lt;/em&gt; and &lt;em&gt;minimum EEC version&lt;/em&gt; of &lt;code&gt;1.343.0&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;This version includes a breaking change for Dynatrace on Grail.
&lt;ul&gt;
&lt;li&gt;With the inclusion of OpenPipeline processing rules, any metrics ingested from the extension will be processed by a dedicated OpenPipeline pipeline.&lt;/li&gt;
&lt;li&gt;This means that any dynamic route configured to process any metrics from the extension will be dropped in favor of the dedicated pipeline. Please, refer to &lt;a href="https://docs.dynatrace.com/docs/platform/openpipeline/concepts/pipeline-groups"&gt;pipeline groups&lt;/a&gt; to continue using dynamic routes.&lt;/li&gt;
&lt;li&gt;Additionally, some field names are &lt;a href="https://docs.dynatrace.com/docs/platform/openpipeline/concepts/processing#pipeline"&gt;handled differently&lt;/a&gt; in OpenPipeline, e.g. capitalization. Please double-check any custom dashboards and alerts you have created for this extension.&lt;/li&gt;
&lt;li&gt;You must opt-in to OpenPipeline configuration via Settings API – see the &lt;a href="https://docs.dynatrace.com/docs/shortlink/openpipeline-migration-settings"&gt;documentation&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Metrics &lt;code&gt;kafka.consumer.consumer-metrics.records-lag&lt;/code&gt;, &lt;code&gt;kafka.consumer.consumer-metrics.records-lag-avg&lt;/code&gt; and &lt;code&gt;kafka.consumer.consumer-metrics.records-lag-max&lt;/code&gt; now belong to the new &lt;code&gt;consumer-records-lag&lt;/code&gt; feature set.&lt;/li&gt;
&lt;li&gt;Metrics &lt;code&gt;kafka.consumer.consumer-metrics.records-consumed-rate&lt;/code&gt; and &lt;code&gt;kafka.consumer.consumer-metrics.bytes-consumed-rate&lt;/code&gt; now always split by topic, and new metrics &lt;code&gt;kafka.consumer.consumer-metrics.records-consumed-rate-total&lt;/code&gt; and &lt;code&gt;kafka.consumer.consumer-metrics.bytes-consumed-rate-total&lt;/code&gt;, which do not split by topic, have been added.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;New in this version:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.dynatrace.com/docs/platform/grail/smartscape-on-grail"&gt;Smartscape on Grail&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Added feature set metadata for recommended metrics.&lt;/li&gt;
&lt;li&gt;This extension is now using all rich visualization features of Grail within Infrastructure &amp;amp; Operations App.&lt;/li&gt;
&lt;li&gt;Added new metrics:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;kafka.server.tenant-metrics.consumer-lag-offsets&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;kafka.log.Log.LogEndOffset&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;kafka.cluster.Partition.ObserversInIsrCount&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;kafka.cluster.Partition.IsNotCaughtUp&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;kafka.cluster.Partition.CaughtUpReplicasCount&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;kafka.cluster.Partition.ObserverReplicasCount&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;kafka.consumer.consumer-fetch-manager-metrics.fetch-throttle-time-avg&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;kafka.producer.producer-metrics.produce-throttle-time-avg&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 12 Aug 2026 09:16:32 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.5.0</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;h4&gt;✨ New in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Added new metric &lt;code&gt;kafka.consumer.consumer-metrics.assigned-partitions&lt;/code&gt; to monitor Kafka partitions unassigned to consumers.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;🐛 Fixed in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Links from the included &lt;strong&gt;Dashboard&lt;/strong&gt; to entity lists now point to the right path for the Infrastructure &amp;amp; Operations App.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 18 Mar 2026 15:05:38 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.4.0</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;h3&gt;New in this version:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added ALERT_TEMPLATES for anomaly detectors in the Davis Anomaly Detection app (latest Dynatrace only).&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 19 Dec 2025 21:26:59 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.3.5</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;h3&gt;⚠️ Important Change:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;This release requires a Minimum Dynatrace Version and Minimum ActiveGate version of &lt;code&gt;1.318.0&lt;/code&gt; or higher.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Improved in this version:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Internal metadata updated.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;New in this version:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added 3 new metrics
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;broker-metrics&lt;/code&gt; feature set
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;kafka.server.ReplicaManager.UnderMinIsrPartitionCount&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;code&gt;network-metrics&lt;/code&gt; feature set
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;kafka.network.RequestChannel.ResponseQueueSize.Value&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;kafka.network.SocketServer.NetworkProcessorAvgIdlePercent&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 26 Nov 2025 17:10:12 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.3.3</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Added new broker topic metric &lt;code&gt;Mirror topic bytes in rate&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Added 24 new Confluent platform only metrics:
&lt;ul&gt;
&lt;li&gt;12 new &lt;a href="https://docs.confluent.io/platform/current/multi-dc-deployments/cluster-linking/metrics.html"&gt;cluster linking&lt;/a&gt; metrics
&lt;ul&gt;
&lt;li&gt;Active link count&lt;/li&gt;
&lt;li&gt;Active mirror count&lt;/li&gt;
&lt;li&gt;Cluster link max lag&lt;/li&gt;
&lt;li&gt;Fetched bytes per second&lt;/li&gt;
&lt;li&gt;Fetched throttle time&lt;/li&gt;
&lt;li&gt;Active task count&lt;/li&gt;
&lt;li&gt;Failed reverse connection count&lt;/li&gt;
&lt;li&gt;Authentication problems&lt;/li&gt;
&lt;li&gt;Unavailable link (by reason)&lt;/li&gt;
&lt;li&gt;Controller reverse connection count&lt;/li&gt;
&lt;li&gt;Controller reverse connection count&lt;/li&gt;
&lt;li&gt;Background thread count&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;12 new &lt;a href="https://docs.confluent.io/platform/current/kafka/monitoring.html#kraft-broker-metrics"&gt;KRaft&lt;/a&gt; metrics
&lt;ul&gt;
&lt;li&gt;Records appended rate&lt;/li&gt;
&lt;li&gt;Commit latency (avg)&lt;/li&gt;
&lt;li&gt;Commit latency (max)&lt;/li&gt;
&lt;li&gt;Record fetch rate&lt;/li&gt;
&lt;li&gt;Log end epoch&lt;/li&gt;
&lt;li&gt;Log end offset&lt;/li&gt;
&lt;li&gt;Current leader ID&lt;/li&gt;
&lt;li&gt;Last applied record offset&lt;/li&gt;
&lt;li&gt;Last applied record timestamp&lt;/li&gt;
&lt;li&gt;Last applied record lag&lt;/li&gt;
&lt;li&gt;Metadata load error count&lt;/li&gt;
&lt;li&gt;Metadata apply error count&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 04 Nov 2025 09:28:30 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.3.1</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;h2&gt;Minimum Dynatrace version now 1.313!&lt;/h2&gt;
&lt;h3&gt;Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Security context attribute on entities&lt;/li&gt;
&lt;li&gt;New Dashboards app dashboard&lt;/li&gt;
&lt;li&gt;Platform ready screen definitions&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 19 Sep 2025 08:30:07 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.2.0</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;h3&gt;Minimum Dynatrace version required has been increased to 1.313&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Connector status and connector task status metrics now show the proper value of the &lt;code&gt;status&lt;/code&gt; dimension.&lt;/li&gt;
&lt;li&gt;Producers and consumers now show the process name instead of the host name on their own name. If running an older version than 1.319 of the OneAgent, the producer/consumer will still show the host's name instead.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 12 Aug 2025 15:04:02 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.1.1</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Added gen3 dashboard&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 18 Mar 2025 07:11:37 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.1.0</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Added new variable &lt;code&gt;Topic name filter&lt;/code&gt; which can be used to filter out the topics that will be monitored.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 11 Mar 2025 14:44:39 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 2.0.0</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;h4&gt;🚀 Improved in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;[🔴 Breaking change]&lt;/strong&gt; Refactored entity creation for &lt;strong&gt;consumers&lt;/strong&gt; and &lt;strong&gt;producers&lt;/strong&gt;. The dimension &lt;code&gt;client-id&lt;/code&gt; is no longer used to generate these entities but only the &lt;code&gt;process_group_instance&lt;/code&gt;and the &lt;code&gt;host&lt;/code&gt; will be considered. This will generate new entity IDs for all your existing consumers and producers, which &lt;strong&gt;will break any configuration (metric events, dashboards, etc.) that use those individual IDs&lt;/strong&gt;. The name of these entities will also change, as it was based on the &lt;code&gt;client-id&lt;/code&gt;previously.&lt;/li&gt;
&lt;li&gt;Charts in consumers and producers have been changed to show metrics per &lt;code&gt;client-id&lt;/code&gt;, instead of per entity.&lt;/li&gt;
&lt;li&gt;Added descriptions to all extension metrics&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;✨ New in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Added 8 new metrics related to the Kafka Connector.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;🐛 Fixed in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;As &lt;code&gt;client-id&lt;/code&gt; is no longer used for generating consumer and producer entities, we no longer run into the entity dimension limitation that prevented new data from being ingested.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 14 Nov 2024 15:04:03 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 1.1.2</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Broker now uses the hostname instead of the host ID, when available.&lt;/li&gt;
&lt;li&gt;Entity lists for broker, producer and consumer now show the host and the process they are related to, as well as allowing you to filter by those entities.&lt;/li&gt;
&lt;li&gt;Removed any reference to zookeeper metrics or entities. To get insight into Zookeeper, activate &lt;a href="https://www.dynatrace.com/hub/detail/apache-zookeeper"&gt;the recently released standalone extension&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 20 Mar 2024 15:25:25 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 1.0.8</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Changed the name of the out-of-the-box alerts to include the word &lt;strong&gt;Kafka&lt;/strong&gt; in the title for increased accessibility.&lt;/li&gt;
&lt;li&gt;Added the following metrics under the &lt;strong&gt;zookeeper-metrics&lt;/strong&gt; feature set:
&lt;ul&gt;
&lt;li&gt;kafka.zookeeper.server.maxRequestLatency&lt;/li&gt;
&lt;li&gt;kafka.zookeeper.server.minRequestLatency&lt;/li&gt;
&lt;li&gt;kafka.zookeeper.server.avgRequestLatency&lt;/li&gt;
&lt;li&gt;kafka.zookeeper.server.aliveConnections&lt;/li&gt;
&lt;li&gt;kafka.zookeeper.server.packetsReceived.count&lt;/li&gt;
&lt;li&gt;kafka.zookeeper.server.packetsSent.count&lt;/li&gt;
&lt;li&gt;kafka.zookeeper.server.outstandingRequests&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added custom topology for the zookeeper&lt;/li&gt;
&lt;li&gt;Added UA screens for the zookeeper&lt;/li&gt;
&lt;li&gt;Modified the out-of-the-box dashboard to include data about the zookeeper&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 06 Feb 2024 14:44:14 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 1.0.7</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Added a new metric &lt;strong&gt;kafka.consumer.consumer-metrics.records-lag&lt;/strong&gt; to show latest consumer lag instead of the already available consumer lag average and maximum.&lt;/li&gt;
&lt;li&gt;Removed the &lt;strong&gt;status&lt;/strong&gt; dimension from the &lt;strong&gt;kafka.connector.status&lt;/strong&gt; and &lt;strong&gt;kafka.connector.task.status&lt;/strong&gt; as the framework is not ready to report such dimensions. The metrics now report 1 when the status is &lt;strong&gt;running&lt;/strong&gt; or 0 otherwise.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Mon, 20 Nov 2023 17:41:57 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 1.0.5</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Fixed a bug where &lt;strong&gt;consumer-fetch-manager-metrics&lt;/strong&gt; where not being captured correctly.&lt;/li&gt;
&lt;li&gt;Added connector task status to metrics.&lt;/li&gt;
&lt;li&gt;Replace entity lists for Host and Process Group Instance with properties in broker, consumer and producer screens.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 26 Sep 2023 14:23:42 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 1.0.4</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Fixed a bug where metrics for &lt;strong&gt;kafka.consumer:type=consumer-fetch-manager-metrics&lt;/strong&gt; where not being populated:
&lt;ul&gt;
&lt;li&gt;kafka.consumer.consumer-metrics.records-lag-avg&lt;/li&gt;
&lt;li&gt;kafka.consumer.consumer-metrics.records-lag-max&lt;/li&gt;
&lt;li&gt;kafka.consumer.consumer-metrics.records-consumed-rate&lt;/li&gt;
&lt;li&gt;kafka.consumer.consumer-metrics.bytes-consumed-rate&lt;/li&gt;
&lt;li&gt;kafka.consumer.consumer-metrics.fetch-latency-avg&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 22 Sep 2023 08:50:29 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 1.0.3</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Add topic dimension to existing metrics:
&lt;ul&gt;
&lt;li&gt;kafka.server.BrokerTopicMetrics.BytesInPerSec.OneMinuteRate&lt;/li&gt;
&lt;li&gt;kafka.server.BrokerTopicMetrics.BytesOutPerSec.OneMinuteRate&lt;/li&gt;
&lt;li&gt;kafka.server.BrokerTopicMetrics.MessagesInPerSec.OneMinuteRate&lt;/li&gt;
&lt;li&gt;kafka.server.BrokerTopicMetrics.TotalProduceRequestsPerSec.OneMinuteRate&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Add new metrics:
&lt;ul&gt;
&lt;li&gt;kafka.server.BrokerTopicMetrics.TotalFollowerFetchRequestsPerSec.OneMinuteRate&lt;/li&gt;
&lt;li&gt;kafka.server.BrokerTopicMetrics.ProduceMessageConversionsPerSec.OneMinuteRate&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Modified UA screens to include the metrics and dimensions listed above:
&lt;ul&gt;
&lt;li&gt;Kafka Broker screen&lt;/li&gt;
&lt;li&gt;Kafka Topic screen&lt;/li&gt;
&lt;li&gt;Host injected tile&lt;/li&gt;
&lt;li&gt;Process Group Instance injected tile&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 15 Sep 2023 10:56:02 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 1.0.1</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description>&lt;ul&gt;
&lt;li&gt;Kafka Server - Current follower lag: Fixed typo in metric key, changed from &lt;strong&gt;kafka.server.FetcherLagMetrics.CosumerLag.Value&lt;/strong&gt; to &lt;strong&gt;kafka.server.FetcherLagMetrics.ConsumerLag.Value&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;This is a breaking change if you're using this metric in dashboards, metric events or other configurations. You will need to reference the new key.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added connector status metric&lt;/li&gt;
&lt;li&gt;Added primary entity for most metrics&lt;/li&gt;
&lt;li&gt;Added navigation card to all screens&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 10 Aug 2023 12:12:30 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item><item><title>Apache Kafka 1.0.0</title><link>https://www.dynatrace.com/hub/detail/apache-kafka/</link><description/><pubDate>Tue, 09 May 2023 08:09:17 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/apache-kafka/</guid></item></channel></rss>