istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix doc broken link (#4627)

This commit is contained in:
Ta-Ching Chen 2019-07-03 22:34:44 +08:00 committed by mergify[bot]
parent affaf1f0ed
commit f47aa85001
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/docs/concepts/observability/index.md
View File

@ -25,7 +25,7 @@ Istio generates the following types of telemetry in order to provide overall ser
of call flows and service dependencies within a mesh.
- [**Access Logs**](#access-logs). As traffic flows into a service within a mesh, Istio can generate a full record of each request, including source and
destination metadata. This information enables operators to audit service behavior down to the individual
[workload instance](http://localhost:1313/docs/reference/glossary/#workload-instance) level.
[workload instance](/docs/reference/glossary/#workload-instance) level.
## Metrics
@ -78,7 +78,7 @@ basic service monitoring needs: latency, traffic, errors, and saturation. Istio
[dashboards](/docs/tasks/telemetry/metrics/using-istio-dashboard/) for monitoring service behaviors based on these metrics.
The [default Istio metrics](/docs/reference/config/policy-and-telemetry/metrics/) are defined by a set of configuration artifacts that ship with Istio and are
exported to [Prometheus](http://localhost:1313/docs/reference/config/policy-and-telemetry/adapters/prometheus/) by default. Operators are free to modify the
exported to [Prometheus](/docs/reference/config/policy-and-telemetry/adapters/prometheus/) by default. Operators are free to modify the
shape and content of these metrics, as well as to change their collection mechanism, to meet their individual monitoring needs.
The [Collecting Metrics](/docs/tasks/telemetry/metrics/collecting-metrics/) task provides more information on customizing Istio metrics generation.