[release-1.22] Remove "Telemetry V2" usages (#15353)

* Remove "Telemetry V2" usages

Signed-off-by: Faseela K <faseela.k@est.tech>

* Update content/en/docs/ops/deployment/performance-and-scalability/index.md

Co-authored-by: John Howard <john.howard@solo.io>

---------

Signed-off-by: Faseela K <faseela.k@est.tech>
Co-authored-by: Faseela K <faseela.k@est.tech>
Co-authored-by: John Howard <john.howard@solo.io>
This commit is contained in:
Istio Automation 2024-06-27 02:53:15 -04:00 committed by GitHub
parent dcdcd63d0f
commit cf5df9af40
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions

View File

@ -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.

View File

@ -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: