Remove [x]PM unless necessary (#4405)

These instructions are now for both LightStep [x]PM and LightStep Tracing.
This commit is contained in:
Robin Whitmore 2019-06-18 17:51:56 -07:00 committed by Martin Taillefer
parent 0b6663f42a
commit a2935ecbd0
1 changed files with 7 additions and 7 deletions

View File

@ -1,6 +1,6 @@
---
title: LightStep [𝑥]PM
description: How to configure the proxies to send tracing requests to LightStep [𝑥]PM.
title: LightStep
description: How to configure the proxies to send tracing requests to LightStep.
weight: 11
keywords: [telemetry,tracing,lightstep]
---
@ -8,7 +8,7 @@ keywords: [telemetry,tracing,lightstep]
This task shows you how to configure Istio to collect trace spans and send them to [LightStep Tracing](https://lightstep.com/products/) or [LightStep [𝑥]PM](https://lightstep.com/products/).
LightStep lets you analyze 100% of unsampled transaction data from large-scale production software to produce meaningful
distributed traces and metrics that help explain performance behaviors and accelerate root cause analysis.
At the end of this task, Istio sends trace spans from the proxies to a LightStep [𝑥]PM Satellite pool making them
At the end of this task, Istio sends trace spans from the proxies to a LightStep Satellite pool making them
available to the web UI.
This task uses the [Bookinfo](/docs/examples/bookinfo/) sample application as an example.
@ -92,7 +92,7 @@ This task uses the [Bookinfo](/docs/examples/bookinfo/) sample application as an
$ curl http://$GATEWAY_URL/productpage
{{< /text >}}
1. Load the LightStep [𝑥]PM [web UI](https://app.lightstep.com/).
1. Load the LightStep [web UI](https://app.lightstep.com/).
1. Navigate to Explorer.
@ -127,17 +127,17 @@ The LightStep integration does not currently capture spans generated by Istio's
Istio captures traces at a configurable trace sampling percentage. To learn how to modify the trace sampling percentage,
visit the [Distributed Tracing trace sampling section](../overview/#trace-sampling).
When using LightStep [𝑥]PM, we do not recommend reducing the trace sampling percentage below 100%. To handle a high traffic mesh,
When using LightStep, we do not recommend reducing the trace sampling percentage below 100%. To handle a high traffic mesh,
consider scaling up the size of your satellite pool.
## Cleanup
If you are not planning any follow-up tasks, remove the Bookinfo sample application and any LightStep [𝑥]PM secrets
If you are not planning any follow-up tasks, remove the Bookinfo sample application and any LightStep secrets
from your cluster.
1. To remove the Bookinfo application, refer to the [Bookinfo cleanup](/docs/examples/bookinfo/#cleanup) instructions.
1. Remove the secret generated for LightStep [𝑥]PM:
1. Remove the secret generated for LightStep:
{{< text bash >}}
$ kubectl delete secret lightstep.cacert