fix(docs): fix links in documentation files (#2956)

revmag · claude[bot] · web-flow · commit d67542e67337 · 2026-03-24T13:22:03.000+05:30
* fix(docs): fix links in documentation files

* Update data/docs/gcp-monitoring/gcp-clb/logging.mdx

Co-authored-by: claude[bot] &lt;209825114+claude[bot]@users.noreply.github.com&gt;

* Update data/docs/gcp-monitoring/gcp-clb/logging.mdx

Co-authored-by: claude[bot] &lt;209825114+claude[bot]@users.noreply.github.com&gt;

* Update data/docs/opentelemetry-collection-agents/k8s/otel-operator/overview.mdx

Co-authored-by: claude[bot] &lt;209825114+claude[bot]@users.noreply.github.com&gt;

---------

Co-authored-by: claude[bot] &lt;209825114+claude[bot]@users.noreply.github.com&gt;
diff --git a/data/docs/alerts-management/metrics-based-alerts.mdx b/data/docs/alerts-management/metrics-based-alerts.mdx
@@ -1,8 +1,8 @@
 ---
-date: 2024-06-06
+date: 2026-03-24
 id: metrics-based-alerts
-
-title: Metrics based alerts 
+title: Metrics based alerts
+description: Learn how to create metrics-based alerts in SigNoz by defining alert conditions, configuring notification settings, and using practical examples for memory usage, error rate, and latency monitoring.
 ---
 
 A Metric-based alert in SigNoz allows you to define conditions based on metric data and trigger alerts when these conditions are met. Here's a breakdown of the various sections and options available when configuring a Metric-based alert:
@@ -13,11 +13,11 @@ to choose the metric to monitor. The following fields that are available in Metr
 
 - **Metric**: A field to select the specific metric you want to monitor (e.g., CPU usage, memory utilization).
 
-- **Time aggregation**: A field to select the time aggregation function to use for the metric. Learn more about [time aggregation](../../metrics-management/types-and-aggregation/#aggregation)
+- **Time aggregation**: A field to select the time aggregation function to use for the metric. Learn more about [time aggregation](https://signoz.io/docs/metrics-management/types-and-aggregation/#aggregation)
 
 - **WHERE**: A filter field to define specific conditions for the metric. You can apply logical operators like "IN," "NOT IN".
 
-- **Space aggregation**: A field to select the space aggregation function to use for the metric. Learn more about [space aggregation](../../metrics-management/types-and-aggregation/#aggregation)
+- **Space aggregation**: A field to select the space aggregation function to use for the metric. Learn more about [space aggregation](https://signoz.io/docs/metrics-management/types-and-aggregation/#aggregation)
 
 - **[Legend Format](https://signoz.io/docs/userguide/query-builder/#legend-format)**: An optional field to customize the legend's format in the visual representation of the alert.
 
diff --git a/data/docs/cicd/argocd/argocd-metrics.mdx b/data/docs/cicd/argocd/argocd-metrics.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-03-12
+date: 2026-03-24
 title: Monitor ArgoCD 
 
 description: Learn how to configure ArgoCD metrics monitoring and visualization with SigNoz
@@ -124,5 +124,5 @@ If you're not seeing ArgoCD metrics in SigNoz, try the following steps:
    - Ensure you're using a version of ArgoCD that exposes metrics
    - Some metrics might be available only in specific versions
 
-If you continue to experience issues, check the [SigNoz community forum](https://community.signoz.io/) or [open an issue on GitHub](https://github.com/SigNoz/signoz/issues) for further assistance.
+If you continue to experience issues, check the [SigNoz community forum](https://community-chat.signoz.io/) or [open an issue on GitHub](https://github.com/SigNoz/signoz/issues) for further assistance.
 
diff --git a/data/docs/crewai-observability.mdx b/data/docs/crewai-observability.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-01-27
+date: 2026-03-24
 id: crewai-observability-with-opentelemetry
 
 title: Crew AI Observability & Monitoring with OpenTelemetry
@@ -163,7 +163,7 @@ Code-based instrumentation gives you fine-grained control over your telemetry co
 
 CrewAI supports a variety of LLM providers for agent workflows, including OpenAI, Anthropic, Google (Gemini/Vertex AI), Azure, AWS Bedrock, Mistral, Groq, Ollama, and more. See the [full list of supported LLM providers](https://docs.crewai.com/en/concepts/llms).
 
-Based on which LLM provider you're using with CrewAI, you'll need to install the corresponding OpenInference instrumentor to track LLM-related traces. See the [OpenInference documentation](https://arize.com/docs/ax/observe/tracing/tracing-concepts/what-is-openinference) for available instrumentors.
+Based on which LLM provider you're using with CrewAI, you'll need to install the corresponding OpenInference instrumentor to track LLM-related traces. See the [OpenInference documentation](https://arize.com/docs/ax/observe/tracing/configure-tracing-options/instrument-with-openinference-helpers) for available instrumentors.
 
 For this example using OpenAI:
 
diff --git a/data/docs/gcp-monitoring/gcp-clb/logging.mdx b/data/docs/gcp-monitoring/gcp-clb/logging.mdx
@@ -1,7 +1,7 @@
 ---
-date: 2024-08-14
+date: 2026-03-24
 id: logging
-
+description: Learn how to collect Google Cloud Load Balancer logs with Pub/Sub, route them through the OpenTelemetry Collector
 title: Cloud Load Balancer Logging
 hide_table_of_contents: true
 ---
@@ -31,11 +31,11 @@ This documentation provides a detailed walkthrough on how to set up a Pub/Sub to
 
 ### Create a Pub/Sub topic
 
-Follow the steps mentioned in the [Creating Pub/Sub Topic](https://signoz.iohttps://signoz.io/docs/gcp-monitoring/bootstrapping/pubsub-topic-creation//) document to create the Pub/Sub topic.
+Follow the steps mentioned in the [Creating Pub/Sub Topic](https://signoz.io/docs/gcp-monitoring/bootstrapping/pubsub-topic-creation/) document to create the Pub/Sub topic.
 
 ### Create Log Router to Pub/Sub Topic
 
-Follow the steps mentioned in the [Log Router Setup](https://signoz.iohttps://signoz.io/docs/gcp-monitoring/bootstrapping/log-router-setup//) document to create the Log Router.
+Follow the steps mentioned in the [Log Router Setup](https://signoz.io/docs/gcp-monitoring/bootstrapping/log-router-setup/) document to create the Log Router.
 
 To ensure you filter out only the Load Balancer logs, use the following filter conditions:
 
diff --git a/data/docs/infrastructure-monitoring/user-guides/telemetry-data-requirements.mdx b/data/docs/infrastructure-monitoring/user-guides/telemetry-data-requirements.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-03-12
+date: 2026-03-24
 id: telemetry-data-requirements
 title: Telemetry Data Requirements for Infrastructure Monitoring
 description: Mandatory resource attributes, metric dependencies, and known platform limitations that control the Infrastructure Monitoring.
@@ -47,5 +47,5 @@ EKS Fargate and some managed Kubernetes clusters block kubelet metric scraping b
 3. Check if kubelet scraping is allowed on the platform.
 
 ## Next Steps
-- [OpenTelemetry Collection Agents Overview](/docs/opentelemetry-collection-agents/get-started/)
-- [k8s-infra OpenTelemetry Collection Agent Guide](/docs/opentelemetry-collection-agents/k8s/k8s-infra/overview/)
+- [OpenTelemetry Collection Agents Overview](https://signoz.io/docs/opentelemetry-collection-agents/get-started/)
+- [k8s-infra OpenTelemetry Collection Agent Guide](https://signoz.io/docs/opentelemetry-collection-agents/k8s/k8s-infra/overview/)
diff --git a/data/docs/inkeep-monitoring.mdx b/data/docs/inkeep-monitoring.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-01-27
+date: 2026-03-24
 id: inkeep-monitoring-with-opentelemetry
 
 title: Inkeep Monitoring & Observability with OpenTelemetry
diff --git a/data/docs/instrumentation/manual-instrumentation/golang/manual-instrumentation.mdx b/data/docs/instrumentation/manual-instrumentation/golang/manual-instrumentation.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-03-06
+date: 2026-03-24
 id: golang-manual-instrumentation
 title: How to add manual instrumentation in Go
 description: Create custom spans, enrich them, and record errors in Go applications with OpenTelemetry and SigNoz
@@ -17,7 +17,7 @@ Manual instrumentation gives you fine-grained control when automatic instrumenta
 
 - Finish the core Go setup in the [OpenTelemetry Go instrumentation guide](https://signoz.io/docs/instrumentation/opentelemetry-golang/) so exporters, tracer provider, and propagators are configured.
 - Propagate `context.Context` through handlers and business logic. Manual spans derive from these contexts so traces stay connected.
-- Tested with <a href="https://go.dev/doc/go1.25.1" target="_blank" rel="noopener noreferrer nofollow">Go 1.25.1</a> and OpenTelemetry Go SDK <a href="https://pkg.go.dev/go.opentelemetry.io/otel/sdk@v1.38.0" target="_blank" rel="noopener noreferrer nofollow">v1.38.0</a>.
+- Tested with <a href="https://go.dev/doc/go1.25" target="_blank" rel="noopener noreferrer nofollow">Go 1.25.1</a> and OpenTelemetry Go SDK <a href="https://pkg.go.dev/go.opentelemetry.io/otel/sdk@v1.38.0" target="_blank" rel="noopener noreferrer nofollow">v1.38.0</a>.
 ## Step 1. Create manual spans
 
 Use the SDK tracer to wrap important work inside custom spans:
diff --git a/data/docs/integrations/aws-rds-postgres.mdx b/data/docs/integrations/aws-rds-postgres.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-03-12
+date: 2026-03-24
 id: aws-rds-postgresql
 title: AWS RDS (PostgreSQL) Metrics and Logs
 description: Collect AWS RDS PostgreSQL metrics and logs using OpenTelemetry Collector and send them to SigNoz for monitoring and analysis.
diff --git a/data/docs/integrations/nomad.mdx b/data/docs/integrations/nomad.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2025-10-10
+date: 2026-03-24
 id: nomad
 
 title: Monitor HashiCorp Nomad with SigNoz
@@ -15,7 +15,7 @@ HashiCorp Nomad is a flexible, enterprise-grade cluster scheduler. Monitoring No
 
 ## Step 1: Enable Nomad Metrics Endpoint
 
-Nomad exposes metrics via a [Prometheus-compatible endpoint](https://developer.hashicorp.com/nomad/docs/telemetry).  
+Nomad exposes metrics via a [Prometheus-compatible endpoint](https://developer.hashicorp.com/nomad/docs/configuration/telemetry).  
 Ensure telemetry is enabled in your Nomad agent configuration:
 
 ```hcl
diff --git a/data/docs/langchain-observability.mdx b/data/docs/langchain-observability.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-01-27
+date: 2026-03-24
 id: langchain-observability-with-opentelemetry
 
 title: LangChain & LangGraph Observability & Monitoring with OpenTelemetry
@@ -30,7 +30,7 @@ You can also check out our LangChain SigNoz MCP agent [here](https://github.com/
 
 ## Instrument your LangChain Python application
 
-To capture detailed telemetry from LangChain/LangGraph without modifying your core application logic, we use [OpenInference](https://arize.com/docs/ax/learn/tracing-concepts/what-is-openinference), a community-driven standard that provides pre-built instrumentation for popular AI frameworks like LangChain, built on top of OpenTelemetry. This allows you to trace your LangChain application with minimal configuration.
+To capture detailed telemetry from LangChain/LangGraph without modifying your core application logic, we use [OpenInference](https://arize.com/docs/ax/observe/tracing/configure-tracing-options/instrument-with-openinference-helpers), a community-driven standard that provides pre-built instrumentation for popular AI frameworks like LangChain, built on top of OpenTelemetry. This allows you to trace your LangChain application with minimal configuration.
 
 Check out detailed instructions on how to set up OpenInference instrumentation in your LangChain application over [here](https://pypi.org/project/openinference-instrumentation-langchain/).
 
diff --git a/data/docs/migration/migrate-from-signoz-self-host-to-signoz-cloud.mdx b/data/docs/migration/migrate-from-signoz-self-host-to-signoz-cloud.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-03-12
+date: 2026-03-24
 id: migrate-from-signoz-self-host-to-signoz-cloud
 title: Migrate from Self-Hosted SigNoz to SigNoz Cloud
 description: Step-by-step guide to migrate your observability setup from self-hosted SigNoz to SigNoz Cloud, including telemetry pipelines, dashboards, alerts, and pipelines.
diff --git a/data/docs/opentelemetry-collection-agents/k8s/otel-operator/overview.mdx b/data/docs/opentelemetry-collection-agents/k8s/otel-operator/overview.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2025-08-21
+date: 2026-03-24
 id: overview
 
 title: OpenTelemetry Operator - Overview
@@ -55,7 +55,7 @@ The OpenTelemetry Operator greatly simplifies the process of auto-instrumenting
 
 The operator can inject and configure [OpenTelemetry auto-instrumentation](https://opentelemetry.io/docs/platforms/kubernetes/operator/automatic/) libraries. Currently, Apache HTTPD, .NET, Go, Java, Nginx, Node.js and Python are supported.
 
-To manage automatic instrumentation, the Operator must be configured to identify which pods to instrument and select the appropriate automatic instrumentation for those pods. This configuration is done through the [Instrumentation CRD](https://github.com/open-telemetry/opentelemetry-operator/blob/main/docs/api/instrumentations.md) and adding [Annotations](http://localhost:3000/docs/collection-agents/k8s/otel-operator/install/#annontations-for-auto-instrumentation-injection) to the workloads
+To manage automatic instrumentation, the Operator must be configured to identify which pods to instrument and select the appropriate automatic instrumentation for those pods. This configuration is done through the [Instrumentation CRD](https://github.com/open-telemetry/opentelemetry-operator/blob/main/docs/api/instrumentations.md) and adding [Annotations](https://signoz.io/docs/opentelemetry-collection-agents/k8s/otel-operator/configure/#auto-instrumentation-with-opentelemetry-operator) to the workloads
 
 ## K8s-Infra vs OpenTelemetry Operator
 
diff --git a/data/docs/userguide/heroku_logs_to_signoz.mdx b/data/docs/userguide/heroku_logs_to_signoz.mdx
@@ -1,5 +1,5 @@
 ---
-date: 2026-03-21
+date: 2026-03-24
 title: Stream Logs from Heroku to SigNoz
 description: Stream application logs from Heroku to SigNoz using HTTPS drains. This guide covers setup for both Cloud and Self-Hosted SigNoz instances.
 id: heroku_logs_to_signoz
@@ -37,7 +37,7 @@ Once the drain is added, verify the logs in SigNoz under the Logs tab.
 ## Stream Heroku Logs to Self-Hosted SigNoz
 
 ### 1. Expose a Port in `docker-compose.yaml`
-Modify the [`docker-compose-minimal.yaml`](https://github.com/SigNoz/signoz/blob/main/deploy/docker/docker-compose-minimal.yaml) file to expose port `8081` for receiving logs:
+Modify the [`docker-compose-minimal.yaml`](https://github.com/SigNoz/signoz/blob/main/deploy/docker/docker-compose.yaml) file to expose port `8081` for receiving logs:
 
 ```yaml:/deploy/docker/docker-compose-minimal.yaml {8} 
 ...
