Fix broken links in content (#1135)

* fix links - batch 1 # Conflicts: # next.config.js * fix batch 2 * fix batch 3 * docs(upgrade-0.70): migration guide for v0.70 (#1137) #### Summary - docker volume migration guide for v0.70 Signed-off-by: Prashant Shahi <[email protected]> * docs: migration v0.70 sidebar (#1138) Signed-off-by: Prashant Shahi <[email protected]> * fix: added kafka reciver in pipeline (#1139) * last blog --------- Signed-off-by: Prashant Shahi <[email protected]> Co-authored-by: Prashant Shahi <[email protected]> Co-authored-by: CheetoDa <[email protected]>
SigNoz · Jan 30, 2025 · 73cb335 · 73cb335
1 parent 7586c74
commit 73cb335
Show file tree

Hide file tree

Showing 31 changed files with 59 additions and 82 deletions.
diff --git a/data/blog/N-1-query-distributed-tracing.mdx b/data/blog/N-1-query-distributed-tracing.mdx
@@ -10,10 +10,6 @@ hide_table_of_contents: false
 keywords: [N+1 query problem,performance,distributed tracing,database retrieval]
 ---
 
-<head>
-  <link rel="canonical" href="https://signoz.io/blog/N+1-query-distributed-tracing/"/>
-</head>
-
 
 
 N+1 query problem is a problem in database retrieval where the related entities of an object are queried individually from a database, leading to O(n) queries where n is the number of related entities of the object.

diff --git a/data/blog/centralized-logging.mdx b/data/blog/centralized-logging.mdx
@@ -296,7 +296,7 @@ Some key features of SEM include:
 
 [Splunk](https://www.splunk.com/) is a software platform designed for searching, monitoring, and analyzing machine-generated data. It functions as a centralized hub for managing logs, employing an agent known as the [Splunk Universal Forwarder](https://www.splunk.com/en_us/blog/learn/splunk-universal-forwarder.html) to collect log data from various remote sources. This collected data is then forwarded to Splunk for indexing and consolidation processes. 
 
-Logs can be visualized and correlated in the Splunk Cloud platform and the Splunk Observability platform using the [Log Observer Connect](https://www.splunk.com/en_us/blog/learn/splunk-log-observer.html) feature. This feature seamlessly integrates log data from your Splunk Platform into an intuitive, codeless interface engineered to speed up identification and resolution of issues.
+Logs can be visualized and correlated in the Splunk Cloud platform and the Splunk Observability platform using the [Log Observer Connect](https://www.splunk.com/en_us/products/log-observer-connect.html) feature. This feature seamlessly integrates log data from your Splunk Platform into an intuitive, codeless interface engineered to speed up identification and resolution of issues.
 
 <figure data-zoomable align='center'>
     <img className="box-shadowed-image" src="/img/blog/2023/01/log-observer.webp" alt="Log management in Splunk Logs Observer Connect"/>

diff --git a/data/blog/datadog-alternatives.mdx b/data/blog/datadog-alternatives.mdx
@@ -541,7 +541,7 @@ The future outlook for Datadog is mixed. While its growth is driven by the incre
 
 Read More:
 
-[**How DataDog Pricing Works**](signoz.io/blog/datadog-pricing)
+[**How DataDog Pricing Works**](https://signoz.io/blog/datadog-pricing)
 
 [**SigNoz vs Datadog**](https://signoz.io/product-comparison/signoz-vs-datadog/)
 

diff --git a/data/blog/nodejs-performance-monitoring.mdx b/data/blog/nodejs-performance-monitoring.mdx
@@ -169,7 +169,7 @@ keywords: [NodeJS,NodeJS performance monitoring,full-stack monitoring,vuejs,mong
 
 Node.js is one of the most popular frameworks for server-side programming. As it's based on JavaScript, it's easy to learn and widely used by both enterprises and startups. However, Node.js applications can be prone to issues like memory leaks and high CPU loads due to its dynamically typed, single-threaded nature.
 
-<Figure src="/img/blog/2024/09/NodeJS-performance-monitoring-image.webp" alt="" caption="NodeJS Performance Monitoring" />This makes performance monitoring crucial for Node.js applications. But monitoring just the web servers isn't enough - you need visibility into your entire application stack for robust performance management.
+This makes performance monitoring crucial for Node.js applications. But monitoring just the web servers isn't enough - you need visibility into your entire application stack for robust performance management.
 
 In this tutorial, we'll demonstrate how to implement full-stack monitoring for a MEVN (MongoDB, Express, Vue, Node) application using OpenTelemetry and SigNoz. We'll cover:
 
@@ -337,7 +337,9 @@ cd signoz/deploy/
 
 You can visit our documentation for instructions on how to install SigNoz using Docker Swarm and Helm Charts.
 
-<Figure src="/img/blog/2024/09/NodeJS-performance-monitoring-deploy_docker_documentation.webp" alt="" caption="" />When you are done installing SigNoz, you can access the UI at <a href="http://localhost:3301/" rel="noopener noreferrer nofollow" target="_blank">http://localhost:3301</a>
+<Figure src="/img/blog/common/deploy_docker_documentation.webp" alt="" caption="" />
+
+When you are done installing SigNoz, you can access the UI at <a href="http://localhost:3301/" rel="noopener noreferrer nofollow" target="_blank">http://localhost:3301</a>
 
 <figure data-zoomable align='center'>
 <img src="/img/blog/common/signoz_dashboard_homepage.webp" alt="SigNoz dashboard"/>
@@ -690,14 +692,14 @@ Below we can find the `mevn-signoz` in the list of applications being monitored
 You can monitor calls from your frontend application under the `Traces` tab of SigNoz.
 
 <figure data-zoomable align='center'>
-<img src="/img/blog/2022/06/NodeJS_perf_frontend.webp" alt="Frontned monitoring on SigNoz"/>
+<img src="/img/blog/2022/06/nodejs_perf_frontend.webp" alt="Frontned monitoring on SigNoz"/>
 <figcaption><i>Function calls from frontend being monitored on SigNoz</i></figcaption>
 </figure>
 
 SigNoz comes with out-of-box charts for monitoring application metrics. You can monitor key application metrics like application latency, requests per second, error rate, etc. You can also see the list of top endpoints from your application.
 
 <figure data-zoomable align='center'>
-<img src="/img/blog/2022/06/NodeJS_perf_app_metrics.webp" alt="Application metrics on SigNoz"/>
+<img src="/img/blog/2022/06/nodejs_perf_app_metrics.webp" alt="Application metrics on SigNoz"/>
 <figcaption><i>Monitor application metrics like latency, requests per second, error percentage, etc. with out-of-box charts</i></figcaption>
 </figure>
 
@@ -711,14 +713,14 @@ The `Traces` tab of SigNoz helps you analyze the tracing data collected from you
 SigNoz provides [Flamegraphs and Gantt charts](https://signoz.io/blog/flamegraphs/) to visualize the complete journey of user requests or transactions.
 
 <figure data-zoomable align='center'>
-<img src="/img/blog/2022/06/NodeJS_perf_flamegraphs.webp" alt="Flamegraphs and Gantt Charts on SigNoz"/>
+<img src="/img/blog/2022/06/nodejs_perf_flamegraphs.webp" alt="Flamegraphs and Gantt Charts on SigNoz"/>
 <figcaption><i>Flamegraphs and Gantt charts on SigNoz dashboard help you visualize the complete journey of a user request</i></figcaption>
 </figure>
 
 SigNoz helps you trace database calls too. In the flamegraphs, you can see the calls made to the MongoDB database in the sample app.
 
 <figure data-zoomable align='center'>
-<img src="/img/blog/2022/06/NodeJS_perf_mongodb.webp" alt="Trace database calls on SigNoz"/>
+<img src="/img/blog/2022/06/nodejs_perf_mongodb.webp" alt="Trace database calls on SigNoz"/>
 <figcaption><i>Trace Mongodb database calls with SigNoz</i></figcaption>
 </figure>
 

diff --git a/data/blog/opentelemetry-nginx.mdx b/data/blog/opentelemetry-nginx.mdx
@@ -209,7 +209,7 @@ At the end of the tutorial, setup will be able to track the request from nginx t
 
 We will install SigNoz by [deploying it with Helm charts](https://signoz.io/docs/install/kubernetes/others/).
 
-<Figure src="/img/blog/2024/09/opentelemetry-nginx-deploy_docker_documentation.webp" alt="" caption="" />Pre-requisites:
+<Figure src="/img/blog/common/deploy_docker_documentation.webp" alt="" caption="" />Pre-requisites:
 
 - Running Kubernetes cluster (>= 1.21 version)
 - 8GB of memory

diff --git a/data/blog/opentelemetry-react.mdx b/data/blog/opentelemetry-react.mdx
@@ -241,7 +241,7 @@ cd signoz/deploy/
 
 You can visit our documentation for instructions on how to install SigNoz using Docker Swarm and Helm Charts.
 
-<Figure src="/img/blog/2024/09/opentelemetry-react-deploy_docker_documentation.webp" alt="" caption="" />When you are done installing SigNoz, you can access the UI at <a href="http://localhost:3301/" rel="noopener noreferrer nofollow" target="_blank">http://localhost:3301</a>
+<Figure src="/img/blog/common/deploy_docker_documentation.webp" alt="" caption="" />When you are done installing SigNoz, you can access the UI at <a href="http://localhost:3301/" rel="noopener noreferrer nofollow" target="_blank">http://localhost:3301</a>
 
 <figure data-zoomable align='center'>
 <img src="/img/blog/common/signoz_dashboard_homepage.webp" alt="SigNoz dashboard"/>
@@ -395,13 +395,17 @@ OpenTelemetry is the future for setting up observability for cloud-native apps.
 
 SigNoz is an open-source observability tool that comes with a SaaS-like experience. You can try out SigNoz by visiting its GitHub repo 👇
 
-<Figure src="/img/blog/2024/09/opentelemetry-react-signoz_github.webp" alt="" caption="" />If you are someone who understands more from video, then you can watch the our video tutorial on how to implement OpenTelemetry React libraries and monitor the application with SigNoz.
+<Figure src="/img/blog/common/signoz_github.webp" alt="" caption="" />
+
+If you are someone who understands more from video, then you can watch the our video tutorial on how to implement OpenTelemetry React libraries and monitor the application with SigNoz.
 
 <YouTube id="IsOQxc3wqyc" mute={false} />
 
 If you have any questions or need any help in setting things up, join our slack community and ping us in `#support` channel.
 
-<Figure src="/img/blog/2024/09/opentelemetry-react-join_slack_cta.webp" alt="" caption="" />## FAQs
+<Figure src="/img/blog/common/join_slack_cta.webp" alt="" caption="" />
+
+## FAQs
 
 ### How does OpenTelemetry differ from other monitoring solutions for React?
 

diff --git a/data/blog/opentelemetry-visualization.mdx b/data/blog/opentelemetry-visualization.mdx
@@ -391,7 +391,9 @@ cd signoz/deploy/
 
 You can visit our documentation for instructions on how to install SigNoz using Docker Swarm and Helm Charts.
 
-<Figure src="/img/blog/2024/10/opentelemetry-visualization-deploy_docker_documentation.webp" alt="" caption="" />Once your application is instrumented with OpenTelemetry client libraries, the data can be sent to the SigNoz backend by specifying a specific port on the machine where SigNoz is installed.
+<Figure src="/img/blog/common/deploy_docker_documentation.webp" alt="" caption="" />
+
+Once your application is instrumented with OpenTelemetry client libraries, the data can be sent to the SigNoz backend by specifying a specific port on the machine where SigNoz is installed.
 
 You can then use Signoz to monitor application metrics with out-of-box charts and visualization.
 
@@ -510,7 +512,7 @@ As you implement OpenTelemetry visualization, you may encounter several challeng
     - Problem: Using multiple visualization tools can lead to fragmented insights and increased complexity.
     - Solution: Aim for a consolidated observability platform that can handle metrics, traces, and logs in a unified interface.
 6. **Alert Fatigue**:
-    - Problem: [Too many alerts](signoz.io/blog/alert-fatigue) can lead to important issues being overlooked.
+    - Problem: [Too many alerts](https://signoz.io/blog/alert-fatigue/) can lead to important issues being overlooked.
     - Solution: Use dynamic thresholds, implement alert grouping, and regularly review and refine your alerting rules.
 
 By anticipating and addressing these challenges, you can create a more effective and sustainable OpenTelemetry visualization strategy.

diff --git a/data/blog/opentelemetry-webinar-on-opamp.mdx b/data/blog/opentelemetry-webinar-on-opamp.mdx
@@ -11,11 +11,6 @@ keywords: [opentelemetry,webinar,opamp,signoz,observability]
 ---
 
 
-
-<head>
-  <link rel="canonical" href="https://signoz.io/blog/otel-webinar-opamp/"/>
-</head>
-
 Open Agent Management Protocol (OpAMP) is the emerging open standard to manage a fleet of telemetry agents at scale.
 
 Take a look at the conversation between <a href="https://github.com/serverless-mom" rel="nofollow">Nočnica Mellifera</a> and <a href="https://github.com/srikanthccv/" rel="nofollow">Srikanth</a> as we discuss recent updates to the standard and how you can remotely manage the OpenTelemetry collector with OpAMP.

diff --git a/data/blog/opentelemetry-webinar-on-trace-api.mdx b/data/blog/opentelemetry-webinar-on-trace-api.mdx
@@ -12,11 +12,6 @@ keywords: [opentelemetry,webinar,trace_api,signoz,observability]
 
 
 
-<head>
-  <link rel="canonical" href="https://signoz.io/blog/otel-webinar-opamp/"/>
-</head>
-
-
 Join <a href="https://github.com/serverless-mom" rel="nofollow">Nočnica Mellifera</a> and <a href="https://github.com/srikanthccv/" rel="nofollow">Srikanth</a> to talk in detail about the OpenTelemetry Trace API. We'll talk about adding spans, events, attributes and other extra info, whether it's really possible to replace logs with traces, and more.
 
 

diff --git a/data/blog/structured-logs.mdx b/data/blog/structured-logs.mdx
@@ -280,9 +280,9 @@ Implementing structured logging in your applications requires careful planning a
 
 Select a library that supports structured logging in your programming language. Popular options include:
    - Java: Logback with Logstash encoder
-   - Python: [structlog](signoz.io/guides/structlog)
+   - Python: [structlog](https://signoz.io/guides/structlog)
    - JavaScript: [Winston]((https://signoz.io/blog/winston-logger/))
-   - Go: [Zap](signoz.io/guides/zap-logger) or [Logrus](https://signoz.io/guides/golang-logrus/)
+   - Go: [Zap](https://signoz.io/guides/zap-logger) or [Logrus](https://signoz.io/guides/golang-logrus/)
 
 2. **Define your log structure**: 
 

diff --git a/data/blog/ten-reasons-not-add-observability.mdx b/data/blog/ten-reasons-not-add-observability.mdx
@@ -10,9 +10,6 @@ hide_table_of_contents: false
 keywords: [opentelemetry,signoz,observability]
 ---
 
-<head>
-  <link rel="canonical" href="https://signoz.io/blog/ten-reasons-not-to-add-observability/"/>
-</head>
 
 Everyone talks about the need for observability, it even comes up in board meetings. But let’s talk about the reasons you _shouldn’t_ add observability to production.
 

diff --git a/data/case-study/observability-for-small-teams-and-solopreneurs.mdx b/data/case-study/observability-for-small-teams-and-solopreneurs.mdx
@@ -76,10 +76,6 @@ Shey knew about the importance of distributed tracing in applications having see
 
 <YouTube id="ZWuqBBtCyQo" mute={false} />
 
-<figure data-zoomable align='center'>
-    <img className="box-shadowed-image" src="/img/blog/2024/06/httpscout-shey.mov" alt=""/>
-    <figcaption><i></i></figcaption>
-</figure>
 
 ### Key Benefits
 

diff --git a/data/comparisons/datadog-vs-splunk.mdx b/data/comparisons/datadog-vs-splunk.mdx
@@ -287,7 +287,7 @@ Some other features include error tracking across logs and traces, pattern analy
 
 ### Splunk
 
-Splunk also did not automatically collect logs from my application. It required the installation and configuration of the <a href = "https://docs.splunk.com/Documentation/Forwarder/9.1.0/Forwarder/Abouttheuniversalforwarder" rel="noopener noreferrer nofollow" target="_blank" >Universal Forwarder (UF)</a> to capture logs. Besides that, Splunk generally has impressive log management capabilities. It can integrate ingested data from the different Splunk platforms and data sources into the Splunk Observability Cloud for centralized log management. This is done by the <a href = "https://www.splunk.com/en_us/blog/learn/splunk-log-observer.html" rel="noopener noreferrer nofollow" target="_blank" >Log Observer Connect</a> feature. It allows for the correlation of logs with real-time metrics and traces, and log-based analysis through advanced search, filtering, and visualization of datasets.
+Splunk also did not automatically collect logs from my application. It required the installation and configuration of the <a href = "https://docs.splunk.com/Documentation/Forwarder/9.1.0/Forwarder/Abouttheuniversalforwarder" rel="noopener noreferrer nofollow" target="_blank" >Universal Forwarder (UF)</a> to capture logs. Besides that, Splunk generally has impressive log management capabilities. It can integrate ingested data from the different Splunk platforms and data sources into the Splunk Observability Cloud for centralized log management. This is done by the <a href = "https://www.splunk.com/en_us/products/log-observer-connect.html" rel="noopener noreferrer nofollow" target="_blank" >Log Observer Connect</a> feature. It allows for the correlation of logs with real-time metrics and traces, and log-based analysis through advanced search, filtering, and visualization of datasets.
 
 <figure data-zoomable align="center">
   <img

diff --git a/data/comparisons/graylog-alternatives.mdx b/data/comparisons/graylog-alternatives.mdx
@@ -104,11 +104,9 @@ Better Stack Logs excels in scenarios where ease of use and quick time-to-value
 
 Splunk shines in large enterprise environments with complex IT infrastructures. Its ability to handle massive data volumes and provide deep insights makes it a powerful—albeit often expensive—choice, especially for teams requiring advanced security and analytics features. 
 
-### 4. [Logz.io](http://logz.io/)
+### 4. Logz.io
 
-<Figure src="/img/comparisons/2024/11/graylog-alternatives-Logz.io" alt="[Logz.io" caption="[Logz.io" /> Dashboard - source Logz.io](Article%20Content%20126fcc6bcd1981a3a523d918e1e13c50/Logz.io_Dashboard.webp)
-
-[Logz.io](http://Logz.io) Dashboard - source Logz.io
+<Figure src="/img/comparisons/2024/11/graylog-alternatives-Logz.io_Dashboard.webp" alt="Logz.io Dashboard - source Logz.io" caption="Logz.io Dashboard - source Logz.io" />
 
 [Logz.io](http://logz.io/) offers a cloud-native log management solution built on the ELK (Elasticsearch, Logstash, Kibana) stack. Key features include:
 

diff --git a/data/comparisons/network-security-monitoring-tools.mdx b/data/comparisons/network-security-monitoring-tools.mdx
@@ -376,7 +376,6 @@ How SigNoz Enhances Your NSM Strategy:
 
 To maximize the effectiveness of your NSM tools, follow these best practices 
 
-<Figure src="/img/comparisons/2024/09/network-security-monitoring-tools-napkin-selection_(4" alt="Best Practices for effective network security monitoring tool" caption="Best Practices for effective network security monitoring tool" />.svg)
 
 Best Practices for effective network security monitoring tool
 

diff --git a/data/comparisons/newrelic-vs-splunk.mdx b/data/comparisons/newrelic-vs-splunk.mdx
@@ -124,7 +124,7 @@ Some other log management features New Relic provides include:
 
 Splunk is well known for its log management capabilities, it can manage large volumes of data. Splunk aggregates data from various Splunk platforms into the Splunk Observability Cloud, where it is centrally managed. It didn’t automatically ingest my data like New Relic, I had to set this up manually.
 
-Log management in Splunk can be carried out using the <a href = "https://www.splunk.com/en_us/blog/learn/splunk-log-observer.html" rel="noopener noreferrer nofollow" target="_blank" >Log Observer Connect</a> feature. This allows for the correlation of logs with real-time metrics and traces, and log-based analysis to better understand patterns in your data.
+Log management in Splunk can be carried out using the <a href = "https://www.splunk.com/en_us/products/log-observer-connect.html" rel="noopener noreferrer nofollow" target="_blank" >Log Observer Connect</a> feature. This allows for the correlation of logs with real-time metrics and traces, and log-based analysis to better understand patterns in your data.
 
 <figure data-zoomable align='center'>
     <img className="box-shadowed-image" src="/img/blog/2024/03/newrelic-vs-splunk-log-observer.webp" alt="Log observer in Splunk"/>

diff --git a/data/comparisons/open-source-datadog-alternatives.mdx b/data/comparisons/open-source-datadog-alternatives.mdx
@@ -220,7 +220,7 @@ provider.addSpanProcessor(new SimpleSpanProcessor(new CollectorTraceExporter()))
 provider.register();
 ```
 
-Read the full guide here - [Using SigNoz with NodeJS](signoz.io/opentelemetry/nodejs-tutorial-overview).
+Read the full guide here - [Using SigNoz with NodeJS](https://signoz.io/opentelemetry/nodejs-tutorial-overview).
 
 Once instrumentation is complete, you'll be able to monitor your services in real-time using the SigNoz dashboard. This includes tracking performance metrics, error rates, and detailed traces for requests across your infrastructure.
-Original file line number
+Diff line change
@@ Expand Up / @@ -10,10 +10,6 @@ hide_table_of_contents: false @@
     keywords: [N+1 query problem,performance,distributed tracing,database retrieval]
     ---
-    <head>
-      <link rel="canonical" href="https://signoz.io/blog/N+1-query-distributed-tracing/"/>
-    </head>
     N+1 query problem is a problem in database retrieval where the related entities of an object are queried individually from a database, leading to O(n) queries where n is the number of related entities of the object.
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
Expand Up		@@ -376,7 +376,6 @@ How SigNoz Enhances Your NSM Strategy:

		To maximize the effectiveness of your NSM tools, follow these best practices

		<Figure src="/img/comparisons/2024/09/network-security-monitoring-tools-napkin-selection_(4" alt="Best Practices for effective network security monitoring tool" caption="Best Practices for effective network security monitoring tool" />.svg)

		Best Practices for effective network security monitoring tool

Expand Down