Change links to github

Author: cbos

content/posts/20240126-observability-toolkit/index.md

@@ -60,12 +60,12 @@ I have been using several tools locally for years for all kinds of development a
 
 Last year I was involved in the investigation of major incidents where I used `Promtail`, `Loki` and `Grafana` to find the cause.   
 Colleagues asked: Can you share the setup you use locally? Of course, and I shared an archive with a `docker-compose.yml` and some configuration files.   
-That is what I want to share with [Observability Toolkit](https://github.com/cbos/observability-toolkit)
+That is what I want to share with [Observability Toolkit](https://goto.ceesbos.nl/observability-toolkit)
 
 ### Setup of Observability Toolkit
 The setup of the Observability Toolkit is looks like this:
 ![](setup.png)   
-All the details are described at [https://github.com/cbos/observability-toolkit](https://github.com/cbos/observability-toolkit)
+All the details are described at [https://github.com/cbos/observability-toolkit](https://goto.ceesbos.nl/observability-toolkit)
 
 ### Use cases
 These tools are like a Swiss army knife to me. There are many situations where I have used them to learn about the application and its actual behavior.

content/posts/20240302-grafana-scenes-development-tips/index.md

@@ -151,7 +151,7 @@ Start the server and open Grafana again in your browser.
 ## 6) Link existing data sources
 For developing a useful app you need data to display. Your local setup will not have that by default. Having the right data, makes the development iterations a lot easier.     
 To solve that you can link existing data sources. You can use the data source provisioning.    
-Suppose you locally have the [Observability Toolkit](https://github.com/cbos/observability-toolkit) and want to connect your scenes development, then your setup can look like this:
+Suppose you locally have the [Observability Toolkit](https://goto.ceesbos.nl/observability-toolkit) and want to connect your scenes development, then your setup can look like this:
 
 ![](setup_with_datasource_links.png)
 

content/posts/20240413-replace-promtail-with-alloy/index.md

@@ -21,7 +21,7 @@ aliases:
 An announcement was made at GrafanaCON. [Alloy](https://grafana.com/blog/2024/04/09/grafana-alloy-opentelemetry-collector-with-prometheus-pipelines/) is introduced in the family of Grafana tools. 
 Alloy is an open source distribution of the OpenTelemetry Collector, but is will also replace Promtail.
 
-In the [Observability Toolkit](https://github.com/cbos/observability-toolkit) I use both Promtail and OpenTelemetry Collector, so it makes sense to merge them.   
+In the [Observability Toolkit](https://goto.ceesbos.nl/observability-toolkit) I use both Promtail and OpenTelemetry Collector, so it makes sense to merge them.   
 In this blog post I will replace Promtail with Alloy. In another post I will see how replacing of OpenTelemetry Collector with Alloy will look like.
 
 ![Replace Promtail with Alloy](replace_promtail_with_alloy.png)

content/posts/20250110-application-observability-code-challenges/index.md

@@ -64,7 +64,7 @@ The challenge will be available in a git repository, all prepared to run on your
 The application will already produce some telemetry data with OpenTelemetry.  
 The **challenge** is to find the problem and **extend the observability** to get better insights and also **proof** that a potential **solution works** as expected.
 
-Using the [Observability Toolkit](https://github.com/cbos/observability-toolkit) you can easily spin up OpenTelemetry and Grafana based observability tools.   
+Using the [Observability Toolkit](https://goto.ceesbos.nl/observability-toolkit) you can easily spin up OpenTelemetry and Grafana based observability tools.   
 You can then run a sample application and a test script.   
 In Grafana you can see the first results, then it is up to you to continue. Some hints will be provided.