From c3e07b423ab543b860450e502d2a2210f01991c2 Mon Sep 17 00:00:00 2001 From: Robert Kaussow Date: Mon, 12 Dec 2022 14:36:46 +0100 Subject: [PATCH] ci: fix linkcheck for graylog --- .../2022/how-to-not-migrate-graylog-to-opensearch/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/posts/2022/how-to-not-migrate-graylog-to-opensearch/index.md b/content/posts/2022/how-to-not-migrate-graylog-to-opensearch/index.md index cf35b1e..b54d1de 100644 --- a/content/posts/2022/how-to-not-migrate-graylog-to-opensearch/index.md +++ b/content/posts/2022/how-to-not-migrate-graylog-to-opensearch/index.md @@ -19,7 +19,7 @@ Graylog is a centralized log management solution to capture, store and analyze l -Fortunately, [Graylog](https://docs.graylog.org/) also knows this and recommends users to switch even if it is currently not enforced and ES 7.10 continues to work for now [^elastic] +Fortunately, [Graylog](https://go2docs.graylog.org) also knows this and recommends users to switch even if it is currently not enforced and ES 7.10 continues to work for now [^elastic] . As you usually don't wants to operate software that no longer receives security updates, I have started to look into a migration and prepared the Container and Ansible setup. My fist mistake on this journey was to believe I can just use the latest Opensearch (OS) release. Had I read the documentation [^graylog] more carefully I would have saved myself a lot of trouble... @@ -39,7 +39,7 @@ What annoys me a bit about the whole situation is the back and forth and the rat [^elastic]: https://www.graylog.org/post/graylog-to-add-support-for-opensearch -[^graylog]: https://docs.graylog.org/docs/migrating-to-opensearch +[^graylog]: https://go2docs.graylog.org/5-0/planning_your_deployment/upgrading_to_opensearch.htm [^gl-github]: https://github.com/Graylog2/graylog2-server/issues/11804 [^os-github]: https://github.com/opensearch-project/project-website/issues/661