mirror of https://github.com/istio/istio.io.git
fix(telemetry): add deprecation notices to Mixer tasks (#6635)
Co-authored-by: douglas-reid <douglas-reid@users.noreply.github.com>
This commit is contained in:
Douglas Reid
GitHub
parent
fb50276d14
commit
280e4d9498
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Remotely Accessing Telemetry Addons
|
||||
description: This task shows you how to configure external access to the set of Istio telemetry addons.
|
||||
weight: 99
|
||||
weight: 98
|
||||
keywords: [telemetry,gateway,jaeger,zipkin,tracing,kiali,prometheus,addons]
|
||||
aliases:
|
||||
- /docs/tasks/telemetry/gateways/
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 114 KiB After Width: | Height: | Size: 192 KiB |
|
|
@ -9,7 +9,7 @@ aliases:
|
|||
---
|
||||
|
||||
This task shows you how to setup and use the Istio Dashboard to monitor mesh
|
||||
traffic. As part of this task, you will use the Grafana Istio add-on and
|
||||
traffic. As part of this task, you will use the Grafana Istio addon and
|
||||
the web-based interface for viewing service mesh traffic data.
|
||||
|
||||
The [Bookinfo](/docs/examples/bookinfo/) sample application is used as
|
||||
|
|
@ -111,7 +111,7 @@ the example application throughout this task.
|
|||
### About the Grafana addon
|
||||
|
||||
The Grafana addon is a preconfigured instance of Grafana. The base image
|
||||
([`grafana/grafana:5.2.3`](https://hub.docker.com/r/grafana/grafana/)) has been
|
||||
([`grafana/grafana`](https://hub.docker.com/r/grafana/grafana/)) has been
|
||||
modified to start with both a Prometheus data source and the Istio Dashboard
|
||||
installed. The base install files for Istio, and Mixer in particular, ship with
|
||||
a default configuration of global (used for every service) metrics. The Istio
|
||||
|
|
|
|||
|
|
@ -1,8 +1,13 @@
|
|||
---
|
||||
title: Using Mixer for Telemetry (deprecated)
|
||||
description: Demonstrates how to collect telemetry information from the mesh using Mixer.
|
||||
weight: 89
|
||||
weight: 99
|
||||
aliases:
|
||||
- /docs/examples/telemetry/
|
||||
- /docs/tasks/telemetry/
|
||||
---
|
||||
|
||||
{{< warning >}}
|
||||
Mixer is deprecated. The functionality provided by Mixer is being moved into the Envoy proxies.
|
||||
Use of Mixer with Istio will only be supported through the 1.7 release of Istio.
|
||||
{{</ warning>}}
|
||||
|
|
@ -3,4 +3,8 @@ title: Logs
|
|||
description: Demonstrates the configuration, collection, and processing of Istio mesh logs.
|
||||
weight: 20
|
||||
aliases:
|
||||
---
|
||||
---
|
||||
{{< warning >}}
|
||||
Mixer is deprecated. The functionality provided by Mixer is being moved into the Envoy proxies.
|
||||
Use of Mixer with Istio will only be supported through the 1.7 release of Istio.
|
||||
{{</ warning>}}
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Collecting Logs with Mixer
|
||||
description: This task shows you how to configure Istio to collect and customize logs.
|
||||
description: This task shows you how to configure Istio's Mixer to collect and customize logs.
|
||||
weight: 10
|
||||
keywords: [telemetry,logs]
|
||||
aliases:
|
||||
|
|
@ -8,6 +8,11 @@ aliases:
|
|||
- /docs/tasks/telemetry/logs/collecting-logs/
|
||||
---
|
||||
|
||||
{{< warning >}}
|
||||
Mixer is deprecated. The functionality provided by Mixer is being moved into the Envoy proxies.
|
||||
Use of Mixer with Istio will only be supported through the 1.7 release of Istio.
|
||||
{{</ warning>}}
|
||||
|
||||
This task shows how to configure Istio to automatically gather telemetry for
|
||||
services in a mesh. At the end of this task, a new log stream will be enabled
|
||||
for calls to services within your mesh.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Logging with Mixer and Fluentd
|
||||
description: This task shows you how to configure Istio to log to a Fluentd daemon.
|
||||
description: This task shows you how to configure Istio's Mixer to log to a Fluentd daemon.
|
||||
weight: 90
|
||||
keywords: [telemetry,logging]
|
||||
aliases:
|
||||
|
|
@ -9,6 +9,11 @@ aliases:
|
|||
- /docs/tasks/telemetry/logs/fluentd/
|
||||
---
|
||||
|
||||
{{< warning >}}
|
||||
Mixer is deprecated. The functionality provided by Mixer is being moved into the Envoy proxies.
|
||||
Use of Mixer with Istio will only be supported through the 1.7 release of Istio.
|
||||
{{</ warning>}}
|
||||
|
||||
This task shows how to configure Istio to create custom log entries
|
||||
and send them to a [Fluentd](https://www.fluentd.org/) daemon. Fluentd
|
||||
is an open source log collector that supports many [data
|
||||
|
|
|
|||
|
|
@ -3,4 +3,8 @@ title: Metrics
|
|||
description: Demonstrates the configuration, collection, and processing of Istio mesh metrics using Mixer.
|
||||
weight: 1
|
||||
aliases:
|
||||
---
|
||||
---
|
||||
{{< warning >}}
|
||||
Mixer is deprecated. The functionality provided by Mixer is being moved into the Envoy proxies.
|
||||
Use of Mixer with Istio will only be supported through the 1.7 release of Istio.
|
||||
{{</ warning>}}
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Collecting Metrics
|
||||
description: This task shows you how to configure Istio to collect and customize metrics.
|
||||
title: Collecting Metrics With Mixer
|
||||
description: This task shows you how to configure Istio's Mixer to collect and customize metrics.
|
||||
weight: 10
|
||||
keywords: [telemetry,metrics]
|
||||
aliases:
|
||||
|
|
@ -10,6 +10,11 @@ aliases:
|
|||
- /docs/tasks/observability/metrics/collecting-metrics/
|
||||
---
|
||||
|
||||
{{< warning >}}
|
||||
Mixer is deprecated. The functionality provided by Mixer is being moved into the Envoy proxies.
|
||||
Use of Mixer with Istio will only be supported through the 1.7 release of Istio.
|
||||
{{< /warning>}}
|
||||
|
||||
This task shows how to configure Istio to automatically gather telemetry for
|
||||
services in a mesh. At the end of this task, a new metric will be enabled for
|
||||
calls to services within your mesh.
|
||||
|
|
@ -19,10 +24,37 @@ as the example application throughout this task.
|
|||
|
||||
## Before you begin
|
||||
|
||||
* [Install Istio](/docs/setup) in your cluster and deploy an
|
||||
application. This task assumes that Mixer is setup in a default configuration
|
||||
(`--configDefaultNamespace=istio-system`). If you use a different
|
||||
value, update the configuration and commands in this task to match the value.
|
||||
* [Install Istio](/docs/setup) with Mixer enabled in your cluster and deploy an
|
||||
application.
|
||||
|
||||
The *custom* configuration needed to use Mixer for telemetry is:
|
||||
|
||||
{{< text yaml >}}
|
||||
values:
|
||||
prometheus:
|
||||
enabled: true
|
||||
telemetry:
|
||||
v1:
|
||||
enabled: true
|
||||
v2:
|
||||
enabled: false
|
||||
components:
|
||||
citadel:
|
||||
enabled: true
|
||||
telemetry:
|
||||
enabled: true
|
||||
{{< /text >}}
|
||||
|
||||
Please see the guide on [Customizing the configuration](/docs/setup/install/istioctl/#customizing-the-configuration)
|
||||
for information on how to apply these settings.
|
||||
|
||||
Once the configuration has been applied, confirm a telemetry-focused instance of Mixer is running:
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl -n istio-system get service istio-telemetry
|
||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
istio-telemetry ClusterIP 10.4.31.226 <none> 9091/TCP,15004/TCP,15014/TCP,42422/TCP 80s
|
||||
{{< /text >}}
|
||||
|
||||
## Collecting new metrics
|
||||
|
||||
|
|
@ -159,4 +191,4 @@ rule, and because the rule is in the configured default configuration namespace
|
|||
|
||||
* If you are not planning to explore any follow-on tasks, refer to the
|
||||
[Bookinfo cleanup](/docs/examples/bookinfo/#cleanup) instructions
|
||||
to shutdown the application.
|
||||
to shutdown the application.
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Collecting Metrics for TCP services
|
||||
description: This task shows you how to configure Istio to collect metrics for TCP services.
|
||||
title: Collecting Metrics for TCP services with Mixer
|
||||
description: This task shows you how to configure Istio's Mixer to collect metrics for TCP services.
|
||||
weight: 20
|
||||
keywords: [telemetry,metrics,tcp]
|
||||
aliases:
|
||||
|
|
@ -8,6 +8,11 @@ aliases:
|
|||
- /docs/tasks/telemetry/metrics/tcp-metrics/
|
||||
---
|
||||
|
||||
{{< warning >}}
|
||||
Mixer is deprecated. The functionality provided by Mixer is being moved into the Envoy proxies.
|
||||
Use of Mixer with Istio will only be supported through the 1.7 release of Istio.
|
||||
{{< /warning>}}
|
||||
|
||||
This task shows how to configure Istio to automatically gather telemetry for TCP
|
||||
services in a mesh. At the end of this task, a new metric will be enabled for
|
||||
calls to a TCP service within your mesh.
|
||||
|
|
@ -17,8 +22,36 @@ as the example application throughout this task.
|
|||
|
||||
## Before you begin
|
||||
|
||||
* [Install Istio](/docs/setup) in your cluster and deploy an
|
||||
application.
|
||||
* [Install Istio](/docs/setup) with Mixer enabled in your cluster and deploy an application.
|
||||
|
||||
The *custom* configuration needed to use Mixer for telemetry is:
|
||||
|
||||
{{< text yaml >}}
|
||||
values:
|
||||
prometheus:
|
||||
enabled: true
|
||||
telemetry:
|
||||
v1:
|
||||
enabled: true
|
||||
v2:
|
||||
enabled: false
|
||||
components:
|
||||
citadel:
|
||||
enabled: true
|
||||
telemetry:
|
||||
enabled: true
|
||||
{{< /text >}}
|
||||
|
||||
Please see the guide on [Customizing the configuration](/docs/setup/install/istioctl/#customizing-the-configuration)
|
||||
for information on how to apply these settings.
|
||||
|
||||
Once the configuration has been applied, confirm a telemetry-focused instance of Mixer is running:
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl -n istio-system get service istio-telemetry
|
||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
istio-telemetry ClusterIP 10.4.31.226 <none> 9091/TCP,15004/TCP,15014/TCP,42422/TCP 80s
|
||||
{{< /text >}}
|
||||
|
||||
* This task assumes that the Bookinfo sample will be deployed in the `default`
|
||||
namespace. If you use a different namespace, you will need to update the
|
||||
|
|
|
|||
Loading…
Reference in New Issue