diff --git a/docs/Monitor-your-data/OpenTelemetry/Visualize/Distributed-tracing.md b/docs/Monitor-your-data/OpenTelemetry/Visualize/Distributed-tracing.md index 8af31129..2399f32e 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Visualize/Distributed-tracing.md +++ b/docs/Monitor-your-data/OpenTelemetry/Visualize/Distributed-tracing.md @@ -1,7 +1,5 @@ # Distributed tracing - - ## What is distributed tracing? diff --git a/docs/Monitor-your-data/OpenTelemetry/Visualize/Logs.md b/docs/Monitor-your-data/OpenTelemetry/Visualize/Logs.md index 9afb3fd0..8bea961f 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Visualize/Logs.md +++ b/docs/Monitor-your-data/OpenTelemetry/Visualize/Logs.md @@ -10,7 +10,4 @@ To visualize your logs, simply navigate to OpsPilot in a browser and access the The following example relies on a user having first [instrumented a Python application](/Monitor-your-data/OpenTelemetry/Instrumentation/Python/) to ship data to OpsPilot. -In the OpsPilot **Logging** window, open the **Job** dropdown and select `fib_by_iteration`. All the log messages emitted by the Python code will appear. - - -![!Screenshot](/Monitor-your-data/OpenTelemetry/images/pythonlogs1.png)*Logs supplied by Python* \ No newline at end of file +In the OpsPilot **Logging** window, open the **Job** dropdown and select `fib_by_iteration`. All the log messages emitted by the Python code will appear. \ No newline at end of file diff --git a/docs/Monitor-your-data/OpenTelemetry/Visualize/Metrics.md b/docs/Monitor-your-data/OpenTelemetry/Visualize/Metrics.md index 87b68f7f..be342b3c 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Visualize/Metrics.md +++ b/docs/Monitor-your-data/OpenTelemetry/Visualize/Metrics.md @@ -14,6 +14,3 @@ To visualize your OTel metrics, simply navigate to the **Explore** tab in OpsPil The following example relies on a user having first [instrumented a Python application](/Monitor-your-data/OpenTelemetry/Instrumentation/Python/) to ship data to OpsPilot. In the OpsPilot **Explore** window, ensure the metrics datasource is selected. Then either use the **Builder** to find your metric (you can search for `job`: `fib_by_iteration`), or use the following in **Code** search mode: `fib_iteration_counter_total{job="fib_by_iteration"}`. You'll get a graph and table of the metric. - - -![!Screenshot](/Monitor-your-data/OpenTelemetry/images/pythonmetrics.png)*Metrics supplied by Python* diff --git a/docs/Monitor-your-data/OpenTelemetry/Visualize/Traces.md b/docs/Monitor-your-data/OpenTelemetry/Visualize/Traces.md index 7046aad2..68652732 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Visualize/Traces.md +++ b/docs/Monitor-your-data/OpenTelemetry/Visualize/Traces.md @@ -13,7 +13,4 @@ To visualize your OTel traces, simply navigate to OpsPilot and access the **Show In the OpsPilot **Explore** window, ensure the `Traces` datasource is selected. Using the `Search` query type, select `Resource Service Name = fib_by_iteration`. Click the **Run Query** button at the top left to execute the query. -Several `fib-outer` spans will appear. Click on one to open the span split view, which displays the inner spans for that execution. Click any inner span on the right to view more information, including the `iteration` attribute set in the code. - - -![!Screenshot](/Monitor-your-data/OpenTelemetry/images/pythontraces.png)*Traces supplied by Python* \ No newline at end of file +Several `fib-outer` spans will appear. Click on one to open the span split view, which displays the inner spans for that execution. Click any inner span on the right to view more information, including the `iteration` attribute set in the code. \ No newline at end of file