diff --git a/src/content/docs/opentelemetry/best-practices/opentelemetry-otlp.mdx b/src/content/docs/opentelemetry/best-practices/opentelemetry-otlp.mdx
index d3b6a6fe890..2279dc41fd0 100644
--- a/src/content/docs/opentelemetry/best-practices/opentelemetry-otlp.mdx
+++ b/src/content/docs/opentelemetry/best-practices/opentelemetry-otlp.mdx
@@ -289,7 +289,10 @@ Attributes are a recurring concept in OpenTelemetry and OTLP. OpenTelemetry has
 
 The New Relic OTLP endpoint supports the standard attribute definition. Complex types like maps of maps, object arrays, and heterogeneous arrays are not supported. The OpenTelemetry SDKs should only produce data which conforms to the standard attribute definition.
 
-**NOTE**: While the standard attribute definition is generally used, log record attributes are exceptional and support complex values (i.e. log record attributes type is [`map<string, any>`](https://opentelemetry.io/docs/specs/otel/logs/data-model/#field-attributes)). Despite this, New Relic currently only supports log record attributes which conform to the standard attribute definition.
+<Callout variant="important">
+While the standard attribute definition is generally used, log record attributes are exceptional and support complex values (i.e. log record attributes type is [`map<string, any>`](https://opentelemetry.io/docs/specs/otel/logs/data-model/#field-attributes)). Despite this, New Relic currently only supports log record attributes which conform to the standard attribute definition.
+</Callout>
+
 
 ## OTLP response payloads [#payloads]