Replace all post_url with Hugo ref blocks

This commit is contained in:
2024-08-05 01:43:55 +02:00
parent c1f1775c91
commit a2f10236a3
56 changed files with 221 additions and 241 deletions

View File

@ -13,8 +13,8 @@ is convenient, but these companies are sometimes taking away my autonomy and exe
for me it's time to take back a little bit of responsibility for my online social presence, away from centrally hosted services and to
privately operated ones.
In my [[first post]({% post_url 2022-11-20-mastodon-1 %})], I shared some thoughts on how I installed a Mastodon instance for myself. In a
[[followup post]({% post_url 2022-11-24-mastodon-2 %})] I talked about its overall architecture and how one might use Prometheus to monitor
In my [[first post]({{< ref "2022-11-20-mastodon-1" >}})], I shared some thoughts on how I installed a Mastodon instance for myself. In a
[[followup post]({{< ref "2022-11-24-mastodon-2" >}})] I talked about its overall architecture and how one might use Prometheus to monitor
vital backends like Redis, Postgres and Elastic. But Mastodon _itself_ is also an application which can provide a wealth of telemetry using
a protocol called [[StatsD](https://github.com/statsd/statsd)].
@ -84,8 +84,7 @@ minutes, I think I can see lots of nifty data in here.
## Prometheus
At IPng Networks, we use Prometheus as a monitoring observability tool. It's worth pointing out that **statsd** has a few options itself to
visualise data, but considering I already have lots of telemetry in Prometheus and Grafana (see my [[previous post]({% post_url
2022-11-24-mastodon-2 %})]), I'm going to take a bit of a detour, and convert these metrics into the Prometheus _exposition format_, so that
visualise data, but considering I already have lots of telemetry in Prometheus and Grafana (see my [[previous post]({{< ref "2022-11-24-mastodon-2" >}})]), I'm going to take a bit of a detour, and convert these metrics into the Prometheus _exposition format_, so that
they can be scraped on a `/metrics` endpoint just like the others. This way, I have all monitoring in one place and using one tool.
Monitoring is hard enough as it is, and having to learn multiple tools is _no bueno_ :)