fixed broken links (#1349)

Co-authored-by: ankit01-oss <>

blog/2022-03-08-distributed-tracing-nodejs.md

@@ -419,7 +419,7 @@ The traces tab of SigNoz dashboard provides powerful filters to analyze the trac
    width={700}
    />
    
-   SigNoz also provides a detailed view of common <a href = "https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md" rel="noopener noreferrer nofollow" target="_blank" >semantic conventions</a> like HTTP, network, and other attributes.
+   SigNoz also provides a detailed view of common <a href = "https://github.com/open-telemetry/semantic-conventions" rel="noopener noreferrer nofollow" target="_blank" >semantic conventions</a> like HTTP, network, and other attributes.
    
    The end-to-end tracing of user requests can help you to identify latency issues quickly.
 

blog/2022-03-09-distributed-tracing-java.md

@@ -416,7 +416,7 @@ width={700}
 />
 
 
-SigNoz also provides a detailed view of common [semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md) like HTTP, network, and other attributes. The end-to-end tracing of user requests can help you to identify latency issues quickly.
+SigNoz also provides a detailed view of common [semantic conventions](https://github.com/open-telemetry/semantic-conventions) like HTTP, network, and other attributes. The end-to-end tracing of user requests can help you to identify latency issues quickly.
 
 
 ## Conclusion

blog/2022-04-13-opentelemetry-grpc-golang.md

@@ -339,12 +339,12 @@ You will see the flamegraph of the selected event, which shows how the request t
 
 <div><br></br></div>
 
-SigNoz also provides a detailed view of common [semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/rpc.md#grpc) like rpc service, method, net, status_code etc. The end-to-end tracing of user requests can help you to identify latency issues quickly.
+SigNoz also provides a detailed view of common [semantic conventions](https://opentelemetry.io/docs/specs/semconv/rpc/grpc/) like rpc service, method, net, status_code etc. The end-to-end tracing of user requests can help you to identify latency issues quickly.
 
 **MongoDB Traces and its semantic conventions**<br></br>
 Establishing a sequential flow of the query and info on the time taken by each part of the request can help quickly identify latency issues. For example, you can see details like how much time the find query took. You can also see the related MongoDB query.
 
-It also provides the [semantic_conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md#mongodb) of MongoDB in the below window.
+It also provides the [semantic_conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/README.md) of MongoDB in the below window.
 
 <!-- ![Untitled](Ashu%20-%20Mon%2092dcf/Untitled%2010.webp) -->
 

blog/2022-06-24-opentelemetry-backend.md

@@ -106,7 +106,7 @@ Below is the list of factors that should be taken into consideration before sele
   | http.target | The full request target as passed in an HTTP request line or equivalent | /blog/june/ |
   | http.scheme | The URI scheme that identifies the used protocol | http; https |
         
-  An OpenTelemetry backend should have native support to store data with OpenTelemetry semantic conventions. Existing observability vendors usually transform the data collected using OpenTelemetry semantic conventions into their propriety formats. But OpenTelemetry has a <a href = "https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/README.md" rel="noopener noreferrer nofollow" target="_blank">huge list</a> of semantic conventions which might not be fully utilized in such scenarios.
+  An OpenTelemetry backend should have native support to store data with OpenTelemetry semantic conventions. Existing observability vendors usually transform the data collected using OpenTelemetry semantic conventions into their propriety formats. But OpenTelemetry has a <a href = "https://github.com/open-telemetry/semantic-conventions" rel="noopener noreferrer nofollow" target="_blank">huge list</a> of semantic conventions which might not be fully utilized in such scenarios.
 
 - **Should allow aggregates on trace data**<br></br>
   Running aggregates on trace data enables you to create service-centric views. OpenTelemetry also provides you the ability to create custom tags. Combined with custom tags and aggregated trace data gives you a powerful magnifying glass to surface performance issues in your services. For example, you can get the error rate and 99th percentile latency of `customer_type: gold` or `deployment_version: v2` or `external_call: paypal`

blog/2022-06-29-opentelemetry-apm.md

@@ -75,7 +75,7 @@ Below is the list of factors that should be taken into consideration before sele
   | http.target | The full request target as passed in an HTTP request line or equivalent | /blog/june/ |
   | http.scheme | The URI scheme that identifies the used protocol | http; https |
         
-  An OpenTelemetry APM should have native support to store data with OpenTelemetry semantic conventions. Existing observability vendors usually transform the data collected using OpenTelemetry semantic conventions into their propriety formats. But OpenTelemetry has a <a href = "https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/README.md" rel="noopener noreferrer nofollow" target="_blank">huge list</a> of semantic conventions which might not be fully utilized in such scenarios.
+  An OpenTelemetry APM should have native support to store data with OpenTelemetry semantic conventions. Existing observability vendors usually transform the data collected using OpenTelemetry semantic conventions into their propriety formats. But OpenTelemetry has a <a href = "https://github.com/open-telemetry/semantic-conventions" rel="noopener noreferrer nofollow" target="_blank">huge list</a> of semantic conventions which might not be fully utilized in such scenarios.
 
 - **Should allow aggregates on trace data**<br></br>
   Running aggregates on trace data enables you to create service-centric views. OpenTelemetry also provides you the ability to create custom tags. Combined with custom tags and aggregated trace data gives you a powerful magnifying glass to surface performance issues in your services. For example, you can get the error rate and 99th percentile latency of `customer_type: gold` or `deployment_version: v2` or `external_call: paypal`

blog/2023-01-31-opentelemetry-distributed-tracing-part-2.md

@@ -445,7 +445,7 @@ You will be able to see the Flamegraph of the selected span which shows how the
 <br></br>
 
 
-SigNoz also provides a detailed view of common [semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md) like HTTP, network, and other attributes. The end-to-end tracing of user requests can help you to identify latency issues quickly.
+SigNoz also provides a detailed view of common [semantic conventions](https://github.com/open-telemetry/semantic-conventions) like HTTP, network, and other attributes. The end-to-end tracing of user requests can help you to identify latency issues quickly.
 
 
 ## Conclusion

blog/2023-02-24-opentelemetry-nginx.md

@@ -91,8 +91,6 @@ signoz-frontend-57bb96c66f-ch22x                    1/1     Running   0
 
 Now let's see how to build the nginx container image with the OpenTelemetry module.
 
-If you are interested in how to create a kubernetes cluster with a multipass and k3s, checkout this [blog post](https://qdnqn.com/deploying-k3s-with-multipass-and-cloud-init/).
-
 ## Building nginx with the OpenTelemetry module
 
 All the container images are located in `package/docker` directory. Let's inspect the nginx Dockerfile.

blog/2023-06-13-srikanth-signoz.md

@@ -17,7 +17,7 @@ keywords:
 </head>
 
 
-Community events are a great way to meet people and learn what they are upto. I was at [KCD Bangalore](https://community.cncf.io/kcd-bengaluru/) last week and met a bunch of people. Among many conversations, one stood out. An engineer and architect turned entrepreneur was interested in hearing feedback about the new product he has been working on.
+Community events are a great way to meet people and learn what they are upto. I was at KCD Bangalore last week and met a bunch of people. Among many conversations, one stood out. An engineer and architect turned entrepreneur was interested in hearing feedback about the new product he has been working on.
 <!--truncate-->
 
 ![Cover Image](/img/blog/2023/06/srikanth-blog.webp)

docs/userguide/span-details.md

@@ -16,7 +16,7 @@ For each span, SigNoz shows the following details:
 - Start time
 - Duration
 - The list of tags associated with the currently selected span.
-- The list of events associated with the currently selected span. If your application emits events to complement traces, SigNoz will display them on this page. For details about raising events in your code, see the [Events](https://opentelemetry.io/docs/concepts/instrumenting-library/#events) section of the OpenTelemetry website and the [Semantic Code for Exceptions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/exceptions.md) page of the `open-telemetry/opentelemetry-specification` specification repo.
+- The list of events associated with the currently selected span. If your application emits events to complement traces, SigNoz will display them on this page. For details about raising events in your code, see the [Events](https://opentelemetry.io/docs/concepts/instrumenting-library/#events) section of the OpenTelemetry website
 
 The following illustration shows the **Span Details** page:
 

docs/userguide/traces.md

@@ -60,7 +60,7 @@ To specify the function you wish to graph and indicate how the system should gro
 
 ## Filter Spans by Tags/Attributes
 
-Tags/Attributes are key-value pairs that allow you to filter spans by their characteristics. SigNoz supports multi-selection criterion. And the characteristics include, but are not limited to HTTP headers, DB systems, and Messaging destinations etc. For exhaustive list please refer to OpenTelemetry’s semantic conventions described on the [Trace Semantic Conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/README.md) page of the OpenTelemetry specification.
+Tags/Attributes are key-value pairs that allow you to filter spans by their characteristics. SigNoz supports multi-selection criterion. And the characteristics include, but are not limited to HTTP headers, DB systems, and Messaging destinations etc. For exhaustive list please refer to OpenTelemetry’s semantic conventions described on the [Trace Semantic Conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/trace.md) page of the OpenTelemetry specification.
 
 There are two ways in which you can filter traces by tags:
 - You can enter plain text in the **Quick Filter** input box and then select the **Run** button at the far right. Note that text is interpreted as case-sensitive.

learn/2021-11-10-observability-stats.md

@@ -77,7 +77,7 @@ The advantages that the cloud brings come at the cost of increased application c
 
 What you need is visibility into your hybrid cloud infra and rich context for every user requests. A robust observability stack can get engineering teams the context to resolve issues faster and earlier.
 
-19. 94% of software leaders say observability is key to developing software. (<a href = "https://newrelic.com/more-perfect-software/more-perfect-software/" rel="noopener noreferrer nofollow" target="_blank" >New Relic</a>)
+19. 94% of software leaders say observability is key to developing software. (<a href = "https://newrelic.com/resources/report/more-perfect-software" rel="noopener noreferrer nofollow" target="_blank" >New Relic</a>)
 
 20. 99% of leaders say their culture and observability technology allow developers to make quick decisions, without fear of repercussions. (<a href = "https://newrelic.com/resources/ebooks/more-perfect-software-gated" rel="noopener noreferrer nofollow" target="_blank" >New Relic</a>)