ci: fix linkcheck for graylog

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
 
 <!--more-->
 
-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 <!-- spellchecker-disable -->[^elastic]<!-- spellchecker-enable -->
+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 <!-- spellchecker-disable -->[^elastic]<!-- spellchecker-enable -->
 . 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 <!-- spellchecker-disable -->[^graylog]<!-- spellchecker-enable -->
 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
 <!-- spellchecker-disable -->
 
 [^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