From b8d8617bee61b6576c5a20777481e8e7cf7347dc Mon Sep 17 00:00:00 2001 From: Hisar Balik Date: Thu, 19 Jan 2023 14:00:14 +0100 Subject: [PATCH] Update docs/01-overview/main-areas/telemetry/telemetry-03-traces.md Co-authored-by: Natalia Sitko <80401180+nataliasitko@users.noreply.github.com> --- docs/01-overview/main-areas/telemetry/telemetry-03-traces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01-overview/main-areas/telemetry/telemetry-03-traces.md b/docs/01-overview/main-areas/telemetry/telemetry-03-traces.md index 50a1b22ff80e..fc44de3a91c5 100644 --- a/docs/01-overview/main-areas/telemetry/telemetry-03-traces.md +++ b/docs/01-overview/main-areas/telemetry/telemetry-03-traces.md @@ -279,7 +279,7 @@ The used buffers are volatile, and the data can be lost on the otel-collector in Only one TracePipeline resource at a time is supported at the moment. ### System span filtering -System related spans reported by Istio will be filtered out without option to opt-out, especially the following: +System-related spans reported by Istio are filtered out without the opt-out option. Here are a few examples of such spans: - `/healtz` endpoint of a component deployed in the `kyma-system` Namespace - `/metrics` endpoint of a component deployed in the `kyma-system` Namespace - All outgoing spans reported by Grafana and Jaeger