From cc791d125fc2c251a9d30d52ef4a6e8a2be7eb1f Mon Sep 17 00:00:00 2001
From: Sanjalee Patni <156739014+Sanjalee-NewRelic@users.noreply.github.com>
Date: Fri, 7 Feb 2025 15:40:24 +0530
Subject: [PATCH] Update opentelemetry-best-practices-resources.mdx

---
 ...opentelemetry-best-practices-resources.mdx | 20 +++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx b/src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
index 244ce331699..cde55093f37 100644
--- a/src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
+++ b/src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
@@ -184,6 +184,26 @@ the following attributes for a relationship to be generated:
 * `span.kind`: This relationship is generated from span data where `span.kind`
   is `producer` or `consumer`.
 
+#### Amazon Managed Kafka (MSK)
+
+The Amazon CloudWatch Metric Streams integration for
+[MSK](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-managed-kafka-msk-integration)
+generates MSK entities in New Relic. These entities will have the
+following entity tag:
+
+* `aws.clusterName` or `aws.kafka.ClusterName`
+* `aws.awsRegion` or `aws.region`
+* `aws.topic` or `aws.kafka.Topic`
+
+If your services use OpenTelemetry instrumentation for MSK it must have
+the following attributes for a relationship to be generated:
+
+* `messaging.destination.name`: The MSK topic to which the service is either producing messages or consuming messages.
+* `server.address`: This attribute must match the corresponding endpoint tag
+  of the MSK entity.
+* `span.kind`: This relationship is generated from span data where `span.kind`
+  is `producer` or `consumer`.
+
 ## Adding custom tags to an entity [#tags]
 
 You can use tags to organize and filter your entities in the UI.