mirror of https://github.com/istio/istio.io.git
Remove In-Depth Telemetry Example (#3352)
* Remove In-Depth Telemetry Example * Add alias for removed doc
This commit is contained in:
parent
ed54669247
commit
9622e6162d
|
|
@ -1,59 +0,0 @@
|
|||
---
|
||||
title: In-Depth Telemetry
|
||||
description: Demonstrates how to obtain uniform metrics, logs, traces across different services using Istio Mixer and Istio sidecar.
|
||||
weight: 30
|
||||
keywords: [telemetry,metrics,logging,tracing]
|
||||
aliases:
|
||||
- /docs/guides/telemetry/index.html
|
||||
---
|
||||
|
||||
This example demonstrates how to obtain uniform metrics, logs, traces across different services using Istio Mixer and Istio sidecar.
|
||||
|
||||
## Overview
|
||||
|
||||
Deploying a microservice-based application in an Istio service mesh allows one
|
||||
to externally control service monitoring and tracing, request (version) routing, resiliency testing,
|
||||
security and policy enforcement, etc., in a consistent way across the services,
|
||||
for the application as a whole.
|
||||
|
||||
In this example, we will use the [Bookinfo sample application](/docs/examples/bookinfo/)
|
||||
to show how operators can obtain uniform metrics and traces from running
|
||||
applications involving diverse language frameworks without relying on
|
||||
developers to manually instrument their applications.
|
||||
|
||||
## Before you begin
|
||||
|
||||
* Install the Istio control plane by following the instructions
|
||||
corresponding to your platform [installation guide](/docs/setup/).
|
||||
|
||||
* Run the Bookinfo sample application by following the applicable
|
||||
[application deployment instructions](/docs/examples/bookinfo/#deploying-the-application).
|
||||
|
||||
## Tasks
|
||||
|
||||
1. [Collecting metrics](/docs/tasks/telemetry/metrics-logs/)
|
||||
This task will configure Mixer to collect a uniform set of metrics
|
||||
across all services in the Bookinfo application.
|
||||
|
||||
1. [Querying metrics](/docs/tasks/telemetry/querying-metrics/)
|
||||
This task installs the Prometheus add-on for metrics collection and
|
||||
demonstrates querying a configured Prometheus server for Istio metrics.
|
||||
|
||||
1. [Distributed tracing](/docs/tasks/telemetry/distributed-tracing/)
|
||||
We will now use Istio to trace how requests are flowing across services
|
||||
in the application. Distributed tracing speeds up troubleshooting by
|
||||
allowing developers to quickly understand how different services
|
||||
contribute to the overall end-user perceived latency. In addition, it
|
||||
can be a valuable tool to diagnosis and troubleshooting in distributed
|
||||
applications.
|
||||
|
||||
1. [Using the Istio Dashboard](/docs/tasks/telemetry/using-istio-dashboard/)
|
||||
This task installs the Grafana add-on with a preconfigured dashboard
|
||||
for monitoring mesh traffic.
|
||||
|
||||
## Cleanup
|
||||
|
||||
When you're finished experimenting with the Bookinfo sample, you can
|
||||
uninstall it by following the
|
||||
[Bookinfo cleanup instructions](/docs/examples/bookinfo/#cleanup)
|
||||
corresponding to your environment.
|
||||
|
|
@ -2,4 +2,6 @@
|
|||
title: Telemetry
|
||||
description: Demonstrates how to collect telemetry information from the mesh.
|
||||
weight: 30
|
||||
aliases:
|
||||
- /docs/examples/telemetry/
|
||||
---
|
||||
|
|
|
|||
Loading…
Reference in New Issue