From cf5df9af405c986201ad8f206b1fa4f007d4145f Mon Sep 17 00:00:00 2001 From: Istio Automation Date: Thu, 27 Jun 2024 02:53:15 -0400 Subject: [PATCH] [release-1.22] Remove "Telemetry V2" usages (#15353) * Remove "Telemetry V2" usages Signed-off-by: Faseela K * Update content/en/docs/ops/deployment/performance-and-scalability/index.md Co-authored-by: John Howard --------- Signed-off-by: Faseela K Co-authored-by: Faseela K Co-authored-by: John Howard --- .../en/docs/ops/deployment/performance-and-scalability/index.md | 2 +- .../docs/tasks/observability/metrics/customize-metrics/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/ops/deployment/performance-and-scalability/index.md b/content/en/docs/ops/deployment/performance-and-scalability/index.md index 9e311e1896..2946427eea 100644 --- a/content/en/docs/ops/deployment/performance-and-scalability/index.md +++ b/content/en/docs/ops/deployment/performance-and-scalability/index.md @@ -71,7 +71,7 @@ Data plane performance depends on many factors, for example: - Number of proxy worker threads - Protocol - CPU cores -- Number and types of proxy filters, specifically telemetry v2 related filters. +- Various proxy features. In particular, telemetry filters (logging, tracing, and metrics) are known to have a moderate impact. The latency, throughput, and the proxies' CPU and memory consumption are measured as a function of said factors. diff --git a/content/en/docs/tasks/observability/metrics/customize-metrics/index.md b/content/en/docs/tasks/observability/metrics/customize-metrics/index.md index 9ef6b94551..14d431de3f 100644 --- a/content/en/docs/tasks/observability/metrics/customize-metrics/index.md +++ b/content/en/docs/tasks/observability/metrics/customize-metrics/index.md @@ -31,7 +31,7 @@ the example application throughout this task. For installation instructions, see ## Enable custom metrics -To customize telemetry v2 metrics, for example, to add `request_host` +To customize telemetry metrics, for example, to add `request_host` and `destination_port` dimensions to the `requests_total` metric emitted by both gateways and sidecars in the inbound and outbound direction, use the following: