From 4699e092b592d9f7af9cdd7d4031d6650fd9b78b Mon Sep 17 00:00:00 2001 From: Hynek Schlawack Date: Wed, 17 Jul 2024 13:03:32 +0200 Subject: [PATCH] docs: fix links --- docs/frameworks.md | 2 +- docs/logging-best-practices.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/frameworks.md b/docs/frameworks.md index a0a997eb..59fc6c92 100644 --- a/docs/frameworks.md +++ b/docs/frameworks.md @@ -74,7 +74,7 @@ request_started.connect(bind_request_details, app) ## OpenTelemetry -The [Python OpenTelemetry SDK](https://opentelemetry.io/docs/instrumentation/python/) offers an easy API to get the current span, so you can enrich your logs with a straight-forward processor: +The [Python OpenTelemetry SDK](https://opentelemetry.io/docs/languages/python/) offers an easy API to get the current span, so you can enrich your logs with a straight-forward processor: ```python from opentelemetry import trace diff --git a/docs/logging-best-practices.md b/docs/logging-best-practices.md index 39e5b1a2..f018a9f6 100644 --- a/docs/logging-best-practices.md +++ b/docs/logging-best-practices.md @@ -82,9 +82,9 @@ All you have to do is to tell [Logstash] either that your log entries are prepen ### Graylog -[Graylog](https://www.graylog.org/) goes one step further. +[Graylog](https://graylog.org/) goes one step further. It not only supports everything those above do (and then some); you can also directly log JSON entries towards it -- optionally even through an AMQP server (like [RabbitMQ](https://www.rabbitmq.com/)) for better reliability. -Additionally, [Graylog's Extended Log Format](https://docs.graylog.org/docs/gelf) (GELF) allows for structured data which makes it an obvious choice to use together with *structlog*. +Additionally, [Graylog's Extended Log Format](https://go2docs.graylog.org/current/getting_in_log_data/gelf.html) (GELF) allows for structured data which makes it an obvious choice to use together with *structlog*. [elasticsearch]: https://www.elastic.co/elasticsearch