From 97acda6b5326ad438dbd9e8fa29a84e5981b606f Mon Sep 17 00:00:00 2001 From: nbaenam Date: Thu, 31 Oct 2024 16:13:03 +0100 Subject: [PATCH] fix(K8s): Modified the caution note --- .../link-otel-applications-kubernetes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-otel-applications-kubernetes.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-otel-applications-kubernetes.mdx index 411741f0504..26d925da4c5 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-otel-applications-kubernetes.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-otel-applications-kubernetes.mdx @@ -205,7 +205,7 @@ You can choose one of these options to monitor your cluster: You should be able to verify that your configurations are working once you have successfully linked your OpenTelemetry data with your Kubernetes data. - Note that the [Kubernetes summary page](/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page) works when both Kubernetes and APM are monitored either exclusively by New Relic's proprietary agents or entirely by OpenTelemetry. If there is a mix of different instrumentation providers (New Relic and OpenTelemetry), you won't see any data on this page. + Note that the [Kubernetes summary page](/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page) has a limitation. You must monitor Kubernetes and APM with New Relic's proprietary agents or with OpenTelemetry. If you've a mix of different instrumentation providers (New Relic and OpenTelemetry), you won't see any data on this page.