From 199578f91a23f772f5bb08850ef9620fd9a02b74 Mon Sep 17 00:00:00 2001
From: Sanjalee Patni <156739014+Sanjalee-NewRelic@users.noreply.github.com>
Date: Thu, 30 Jan 2025 14:04:02 +0530
Subject: [PATCH] Update opentelemetry-best-practices-resources.mdx

---
 .../best-practices/opentelemetry-best-practices-resources.mdx   | 2 ++
 1 file changed, 2 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 b12aaf46b2a..1840cbde206 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
@@ -146,6 +146,8 @@ The memcacahed cluster entity to which the service is connecting should have the
 * `aws.elasticache.configurationEndpointAddress` or `aws.elasticache.endpointAddress`: AWS connection endpoint of the memcached cluster matching with the span attribute `net.peer.name` of the service.
 * `aws.elasticache.configurationEndpointPort` or `aws.elasticache.endpointPort`: Port number on which memcached cluster is running matching with the span attribute `net.peer.port` of the service.
 
+If the above condition is met, the service map shows the service calling instrumented memcached cluster. If the condition is not met, the service map shows the service calling uninstrumented external service
+
 ## Adding custom tags to an entity [#tags]
 
 You can use tags to organize and filter your entities in the UI.