diff --git a/apps/emqx_bridge_kafka/src/emqx_bridge_kafka_impl_producer.erl b/apps/emqx_bridge_kafka/src/emqx_bridge_kafka_impl_producer.erl
index b358cd42b..fb7fce63c 100644
--- a/apps/emqx_bridge_kafka/src/emqx_bridge_kafka_impl_producer.erl
+++ b/apps/emqx_bridge_kafka/src/emqx_bridge_kafka_impl_producer.erl
@@ -839,7 +839,7 @@ handle_telemetry_event(_EventId, _Metrics, _MetaData, _HandlerConfig) ->
 %% metrics.
 -spec telemetry_handler_id(action_resource_id()) -> binary().
 telemetry_handler_id(ActionResId) ->
-    <<"emqx-bridge-kafka-producer-", ActionResId/binary>>.
+    ActionResId.
 
 uninstall_telemetry_handlers(TelemetryId) ->
     telemetry:detach(TelemetryId).
diff --git a/changes/ee/feat-13452.en.md b/changes/ee/feat-13452.en.md
index 95dae8d32..7b2427329 100644
--- a/changes/ee/feat-13452.en.md
+++ b/changes/ee/feat-13452.en.md
@@ -1 +1,5 @@
-Added to possibility to configure a list of predefined Kafka topics to Kafka producer actions, and also to use templates to define the destination Kafka topic.
+Kafka producer action's `topic` config now supports templates.
+
+The topics must be already created in Kafka. If a message is rendered towards a non-existing topic in Kafka (given Kafka disabled topic auto-creation), the message will fail with an unrecoverable error.  Also, if a message does not contain enough information to render to the configured template (e.g.: the template is `t-${t}` and the message context does not define `t`), this message will also fail with an unrecoverable error. 
+
+This same feature is also available for Azure Event Hubs and Confluent Platform producer integrations.