Ajust links

open-telemetry · Jan 16, 2024 · 6aa6fda · 6aa6fda
1 parent 4d3b5b4
commit 6aa6fda
Show file tree

Hide file tree

Showing 7 changed files with 15 additions and 8 deletions.
diff --git a/content/en/blog/2022/apisix/index.md b/content/en/blog/2022/apisix/index.md
@@ -192,7 +192,7 @@ resulting in a call chain consisting of two spans.
 ### Step 1: Deploy OpenTelemetry
 
 The following uses `docker compose` as an example. For other deployments, see
-[Getting Started](/docs/collector/getting-started/).
+[Quick start](/docs/collector/quick-start/).
 
 You can see the following command to deploy[^1]:
 

diff --git a/content/en/blog/2022/k8s-otel-expose/index.md b/content/en/blog/2022/k8s-otel-expose/index.md
@@ -106,7 +106,7 @@ in this setup are mentioned in brackets.
   [v1.2.1] installed.
 - A Kubernetes [v1.23.3] edge cluster to create a test cluster. Using
   [Kind](https://kind.sigs.k8s.io/) is recommended.
-- Installed [OpenTelemetry Operator](/docs/collector/getting-started) [v0.58.0]
+- Installed [OpenTelemetry Operator](/docs/kubernetes/operator/) [v0.58.0]
   on both ends.
 - Installed [Jaeger Operator](https://www.jaegertracing.io/docs/1.37/operator/)
   [v1.37.0] on your public cluster.

diff --git a/content/en/blog/2023/k8s-runtime-observability/index.md b/content/en/blog/2023/k8s-runtime-observability/index.md
@@ -472,5 +472,5 @@ are available from the Tracetest repository.
 - [Traces For Kubernetes System Components](https://kubernetes.io/docs/concepts/cluster-administration/system-traces/)
 - [Tracing on ContainerD](https://github.com/containerd/containerd/blob/main/docs/tracing.md)
 - [Kubernetes: Tools for Monitoring Resources](https://kubernetes.io/docs/tasks/debug/debug-cluster/resource-usage-monitoring/)
-- [Getting Started with OTel Collector](/docs/collector/getting-started/)
+- [OTel Collector quick start](/docs/collector/quick-start/)
 - [Boosting Kubernetes container runtime observability with OpenTelemetry](https://kubernetes.io/blog/2022/12/01/runtime-observability-opentelemetry/)
diff --git a/content/en/docs/collector/_index.md b/content/en/docs/collector/_index.md
@@ -48,7 +48,7 @@ it allows your service to offload data quickly and the collector can take care
 of additional handling like retries, batching, encryption or even sensitive data
 filtering.
 
-It is also easier to [setup a collector](./getting-started) than you might
+It is also easier to [setup a collector](quick-start) than you might
 think: the default OTLP exporters in each language assume a local collector
 endpoint, so if you launch a collector it will automatically start receiving
 telemetry.

diff --git a/content/en/docs/collector/management.md b/content/en/docs/collector/management.md
@@ -11,7 +11,7 @@ deployment at scale.
 To get the most out of this page you should know how to install and configure
 the collector. These topics are covered elsewhere:
 
-- [Getting Started][otel-collector-getting-started] to understand how to install
+- [Quick Start](/docs/collector/quick-start/) to understand how to install
   the OpenTelemetry Collector.
 - [Configuration][otel-collector-configuration] for how to configure the
   OpenTelemetry Collector, setting up telemetry pipelines.
@@ -217,8 +217,7 @@ otelcol_receiver_refused_metric_points{receiver="prometheus/own_metrics",service
   - [What is OpAMP & What is BindPlane][opamp-bindplane]
 
 [otel-collector]: /docs/collector/
-[otel-collector-getting-started]: /docs/collector/getting-started
-[otel-collector-configuration]: /docs/collector/configuration
+[otel-collector-configuration]: /docs/collector/configuration/
 [opamp-spec]:
   https://github.com/open-telemetry/opamp-spec/blob/main/specification.md
 [opamp-in-otel-collector]:

diff --git a/content/en/docs/languages/python/getting-started.md b/content/en/docs/languages/python/getting-started.md
@@ -640,7 +640,7 @@ emitted to the console, with separate counts for each roll value:
 
 ## Send telemetry to an OpenTelemetry Collector
 
-The [OpenTelemetry Collector](/docs/collector/getting-started/) is a critical
+The [OpenTelemetry Collector](/docs/collector/) is a critical
 component of most production deployments. Some examples of when it's beneficial
 to use a collector:
 

diff --git a/static/refcache.json b/static/refcache.json
@@ -4095,6 +4095,10 @@
     "StatusCode": 200,
     "LastSeen": "2023-09-25T10:17:08.450210292Z"
   },
+  "https://go.dev/doc/code#Command": {
+    "StatusCode": 200,
+    "LastSeen": "2024-01-16T09:38:29.715064-05:00"
+  },
   "https://go.dev/doc/install/gccgo": {
     "StatusCode": 200,
     "LastSeen": "2023-06-29T16:08:23.852746-04:00"
@@ -5195,6 +5199,10 @@
     "StatusCode": 200,
     "LastSeen": "2023-06-29T18:45:36.801594-04:00"
   },
+  "https://pkg.go.dev/cmd/go#hdr-Environment_variables": {
+    "StatusCode": 200,
+    "LastSeen": "2024-01-16T09:38:27.962889-05:00"
+  },
   "https://pkg.go.dev/github.com/mitchellh/mapstructure": {
     "StatusCode": 200,
     "LastSeen": "2023-07-26T16:44:49.203638-04:00"