Docs: Use the correct URLs in various places

diff --git a/doc/05-service-monitoring.md b/doc/05-service-monitoring.md
index 2ee74e0e960cf016d0f0983247a4b003ddf91c27..cdaa8ed1a5981a3a52d2175836daa9f6465e5b8f 100644 (file)
--- a/doc/05-service-monitoring.md
+++ b/doc/05-service-monitoring.md
@@ -93,7 +93,7 @@ For further information on your monitoring configuration read the
 [Monitoring Basics](03-monitoring-basics.md#monitoring-basics) chapter.
 
 If you have created your own `CheckCommand` definition, please kindly
-[send it upstream](https://icinga.com/community/).
+[send it upstream](https://github.com/Icinga/icinga2/blob/master/CONTRIBUTING.md).
 
 ### Plugin API <a id="service-monitoring-plugin-api"></a>
 

diff --git a/doc/06-distributed-monitoring.md b/doc/06-distributed-monitoring.md
index 44e1ae2e343cab3351d006d63b3c0f781f1e49d0..48cfd1b26af8005d2cce4c778beb330a891e688c 100644 (file)
--- a/doc/06-distributed-monitoring.md
+++ b/doc/06-distributed-monitoring.md
@@ -1216,7 +1216,7 @@ If you are eager to start fresh instead you might take a look into the
 The following examples should give you an idea on how to build your own
 distributed monitoring environment. We've seen them all in production
 environments and received feedback from our [community](https://icinga.com/community/)
-and [partner support](https://icinga.com/services/support/) channels:
+and [partner support](https://icinga.com/support/) channels:
 
 * Single master with clients.
 * HA master with clients as command endpoint.

diff --git a/doc/10-icinga-template-library.md b/doc/10-icinga-template-library.md
index aa38ee46fc008399cab2bb4f01d31450256815a2..a9a8616512b3568d5abb6e6004be6fc44244db0d 100644 (file)
--- a/doc/10-icinga-template-library.md
+++ b/doc/10-icinga-template-library.md
@@ -849,7 +849,7 @@ negate_arguments      | **Optional.** Arguments for the negated command.
 
 ### nrpe <a id="plugin-check-command-nrpe"></a>
 
-The `check_nrpe` plugin can be used to query an [NRPE](https://docs.icinga.com/latest/en/nrpe.html)
+The `check_nrpe` plugin can be used to query an [NRPE](https://icinga.com/docs/icinga1/latest/en/nrpe.html)
 server or [NSClient++](https://www.nsclient.org). **Note**: This plugin
 is considered insecure/deprecated.
 

diff --git a/doc/13-addons.md b/doc/13-addons.md
index eaf1af8582ace398b1574bb8961e2088f3b16f5e..7c9623c4bb8d4b6e425a0e26e64ebe4a8c308a31 100644 (file)
--- a/doc/13-addons.md
+++ b/doc/13-addons.md
@@ -71,7 +71,7 @@ A popular frontend for InfluxDB is for example [Grafana](https://grafana.org).
 ### Icinga Reporting <a id="addons-visualization-reporting"></a>
 
 By enabling the [DB IDO](14-features.md#db-ido) feature you can use the
-[Icinga Reporting package](https://docs.icinga.com/latest/en/reporting.html).
+[Icinga Reporting package](https://icinga.com/docs/icinga1/latest/en/reporting.html).
 
 ### NagVis <a id="addons-visualization-nagvis"></a>
 
@@ -118,9 +118,9 @@ There's a variety of resources available, for example different notification scr
 
 Additionally external services can be [integrated with Icinga 2](https://icinga.com/products/integrations/):
 
-* [Pagerduty](https://icinga.com/partners/pagerduty/)
-* [VictorOps](https://icinga.com/partners/victorops/)
-* [StackStorm](https://icinga.com/partners/stackstorm/)
+* [Pagerduty](https://icinga.com/products/integrations/pagerduty/)
+* [VictorOps](https://icinga.com/products/integrations/victorops/)
+* [StackStorm](https://icinga.com/products/integrations/stackstorm/)
 
 More information can be found on the [Icinga Website](https://icinga.com/).
 

diff --git a/doc/21-development.md b/doc/21-development.md
index c7e54878d5f150d04f4699c71e71818af032ae57..d90d50def0da852a00e32a97d84726cd54685fe9 100644 (file)
--- a/doc/21-development.md
+++ b/doc/21-development.md
@@ -167,7 +167,7 @@ running Icinga 2.
     (gdb) handle SIGPIPE nostop noprint pass
     (gdb) r
 
-If you create a [bug report](https://icinga.com/community/),
+If you create a [new issue](https://github.com/Icinga/icinga2/issues),
 make sure to attach as much detail as possible.
 
 ### GDB Backtrace from Running Process <a id="development-debug-gdb-backtrace-running"></a>