fix links and commands

2-lts/step3.md

@@ -78,7 +78,7 @@ The potential duplication of data between Prometheus+sidecar results and store G
 
 Another interesting question here is how to ensure if we query the data from bucket only?
 
-We can check this by visitng the [New UI]({{TRAFFIC_HOST1_9091}}/new/graph?g0.expr=&g0.tab=0&g0.stacked=0&g0.range_input=1h&g0.max_source_resolution=0s&g0.deduplicate=1&g0.partial_response=0&g0.store_matches=[]), inserting `continuous_app_metric0` metrics again with 1 year time range of graph,
+We can check this by visitng the [Query UI]({{TRAFFIC_HOST1_9091}}/graph?g0.expr=&g0.tab=0&g0.stacked=0&g0.range_input=1h&g0.max_source_resolution=0s&g0.deduplicate=1&g0.partial_response=0&g0.store_matches=[]), inserting `continuous_app_metric0` metrics again with 1 year time range of graph,
 and click on `Enable Store Filtering`.
 
 This allows us to filter stores and helps in debugging from where we are querying the data exactly.

2-lts/step4.md

@@ -37,7 +37,7 @@ The flag `wait` is used to make sure all compactions have been processed while `
 
 ## Setup Verification
 
-To check if compactor works fine, we can look at the [Bucket View]({{TRAFFIC_HOST1_19095}}/new/loaded).
+To check if compactor works fine, we can look at the [Bucket View]({{TRAFFIC_HOST1_19095}}/loaded).
 
 Now, if we click on the blocks, they will provide us all the metadata (Series, Samples, Resolution, Chunks, and many more things).
 
@@ -50,7 +50,7 @@ and no special configuration is required to perform this process.
 
 The Compactor applies compaction to the bucket data and also completes the downsampling for historical data.
 
-To expierience this, click on the [Querier]({{TRAFFIC_HOST1_9091}}/new/graph?g0.expr=&g0.tab=0&g0.stacked=0&g0.range_input=1h&g0.max_source_resolution=0s&g0.deduplicate=1&g0.partial_response=0&g0.store_matches=[]) and insert metrics `continuous_app_metric0` with 1 year time range of graph, and also, click on `Enable Store Filtering`.
+To expierience this, click on the [Querier]({{TRAFFIC_HOST1_9091}}/graph?g0.expr=&g0.tab=0&g0.stacked=0&g0.range_input=1h&g0.max_source_resolution=0s&g0.deduplicate=1&g0.partial_response=0&g0.store_matches=[]) and insert metrics `continuous_app_metric0` with 1 year time range of graph, and also, click on `Enable Store Filtering`.
 
 Let's try querying `Max 5m downsampling` data, it uses 5m resolution and it will be faster than the raw data. Also, Downsampling is built on top of data, and never done on **young** data.
 

5-query-caching/step1.md

@@ -80,12 +80,12 @@ scrape_configs:
 for i in $(seq 0 2); do
 docker run -d --net=host --rm \
     -v $(pwd)/prometheus"${i}".yml:/etc/prometheus/prometheus.yml \
-    -v $(pwd)/prometheus_data:/prometheus"${i}" \
+    -v $(pwd)/prometheus_data/prometheus"${i}":/prometheus"${i}" \
     -u root \
     --name prometheus"${i}" \
     quay.io/prometheus/prometheus:v2.38.0 \
     --config.file=/etc/prometheus/prometheus.yml \
-    --storage.tsdb.path=/prometheus \
+    --storage.tsdb.path=/prometheus"${i}" \
     --web.listen-address=:909"${i}" \
     --web.external-url={{TRAFFIC_HOST1_909"${i}"}} \
     --web.enable-lifecycle \

x-playground/step2.md

@@ -170,7 +170,7 @@ docker run -d --net=host --rm \
     --http-address 0.0.0.0:19095
 ```{{execute}}
 
-Visit {{TRAFFIC_HOST1_19095}}/new/loaded to see Compactor Web UI.
+Visit {{TRAFFIC_HOST1_19095}}/loaded to see Compactor Web UI.
 
 ### Data should be immediately downsampled as well for smooth experience!