[-] updating non-functional links in docs (#681)

* updating non-functional links
* fix some links

---------

Co-authored-by: Pavlo Golub <[email protected]>

Author: shubham-j-sde

docs/howto/dashboarding_alerting.md

@@ -2,7 +2,7 @@
 title: Dashboarding and alerting
 ---
 
-# Grafana intro
+## Grafana intro
 
 To display the gathered and stored metrics the pgwatch project has
 decided to rely heavily on the popular Grafana dashboarding solution.
@@ -29,19 +29,19 @@ changes.
 
 **Links:**
 
-[Built-in dashboards for PostgreSQL (TimescaleDB)
+- [Built-in dashboards for PostgreSQL (TimescaleDB)
 storage](https://github.com/cybertec-postgresql/pgwatch/tree/master/grafana/postgres/)
 
-[Screenshots of pgwatch default
-dashboards](https://github.com/cybertec-postgresql/pgwatch/tree/master/docs/screenshots)
+- [Screenshots of pgwatch default
+dashboards](../gallery/dashboards.md)
 
-[The online Demo site](https://demo.pgwatch.com/)
+- [The online Demo site](https://demo.pgwatch.com/)
 
-# Alerting
+## Alerting
 
 Alerting is very conveniently also supported by Grafana in a simple
 point-and-click style - see
-[here](https://grafana.com/docs/grafana/latest/alerting/alerts-overview/)
+[here](https://grafana.com/docs/grafana/latest/alerting/#overview)
 for the official documentation. In general all more popular notification
 services are supported, and it's pretty much the easiest way to quickly
 start with PostgreSQL alerting on a smaller scale. For enterprise usage

docs/howto/using_managed_services.md

@@ -81,6 +81,6 @@ one can for example use the `wal_size` metrics.
 # Aiven for PostgreSQL
 
 The [Aiven developer
-documentation](https://developer.aiven.io/docs/products/postgresql/howto/monitor-with-pgwatch.html)
+documentation](https://aiven.io/docs/products/postgresql/howto/monitor-with-pgwatch2)
 contains information on how to monitor PostgreSQL instances running on
 the Aiven platform with pgwatch.

docs/reference/advanced_features.md

@@ -65,7 +65,7 @@ the whole instance. The metric name to enable log parsing is
 destination / setting to work, the monitoring user needs superuser /
 pg_monitor privileges - if this is not possible then log settings need
 to be specified manually under "Host config" as seen for example
-[here](https://github.com/cybertec-postgresql/pgwatch/blob/master/internal/sources/sample.sources.yaml).
+[here](https://github.com/cybertec-postgresql/pgwatch/blob/master/internal/sources/sample.sources.yaml#L25).
 
 **Sample configuration if not using CSVLOG logging:**
 
@@ -101,7 +101,7 @@ separated via the "database" tag.
 There's also a built-in Grafana dashboard for PgBouncer data, looking
 like that:
 
-[![Grafana dash for PgBouncer stats](https://raw.githubusercontent.com/cybertec-postgresql/pgwatch/master/docs/../gallery/pgbouncer_stats.png)](https://raw.githubusercontent.com/cybertec-postgresql/pgwatch/master/docs/../gallery/pgbouncer_stats.png)
+[![Grafana dash for PgBouncer stats](https://raw.githubusercontent.com/cybertec-postgresql/pgwatch/refs/heads/master/docs/gallery/pgbouncer_stats.png)](https://raw.githubusercontent.com/cybertec-postgresql/pgwatch/refs/heads/master/docs/gallery/pgbouncer_stats.png)
 
 ## Pgpool-II support
 
@@ -114,7 +114,7 @@ Type*, provide connection info to the pooler port and make sure the
 The built-in Grafana dashboard for Pgpool data looks something like
 that:
 
-[![Grafana dash for PgPool stats](https://raw.githubusercontent.com/cybertec-postgresql/pgwatch/master/docs/../gallery/pgpool_status.png)](https://raw.githubusercontent.com/cybertec-postgresql/pgwatch/master/docs/../gallery/pgpool_status.png)
+[![Grafana dash for PgPool stats](https://raw.githubusercontent.com/cybertec-postgresql/pgwatch/refs/heads/master/docs/gallery/pgpool_status.png)](https://raw.githubusercontent.com/cybertec-postgresql/pgwatch/refs/heads/master/docs/gallery/pgpool_status.png)
 
 ## Prometheus scraping
 

docs/tutorial/docker_installation.md

@@ -151,7 +151,7 @@ needed.
 - Some built-in metrics like `"cpu_load"` and others, that gather
     privileged or OS statistics, require installing *helper functions*
     (looking like
-    [that](https://github.com/cybertec-postgresql/pgwatch/blob/master/pgwatch/metrics/00_helpers/get_load_average/9.1/metric.sql)),
+    [that](https://github.com/cybertec-postgresql/pgwatch/blob/master/docs/tutorial/preparing_databases.md?plain=1#L111)),
     so it might be normal to see some blank panels or fetching errors in
     the logs. On how to prepare databases for monitoring see the
     [Monitoring preparations](preparing_databases.md) chapter.