Docs: Use the correct URLs in various places

This commit is contained in:
Michael Friedrich 2018-10-18 09:59:33 +02:00
parent 3cb2c1d143
commit 12ef5c053f
5 changed files with 8 additions and 8 deletions

View File

@ -93,7 +93,7 @@ For further information on your monitoring configuration read the
[Monitoring Basics](03-monitoring-basics.md#monitoring-basics) chapter. [Monitoring Basics](03-monitoring-basics.md#monitoring-basics) chapter.
If you have created your own `CheckCommand` definition, please kindly 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> ### Plugin API <a id="service-monitoring-plugin-api"></a>

View File

@ -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 The following examples should give you an idea on how to build your own
distributed monitoring environment. We've seen them all in production distributed monitoring environment. We've seen them all in production
environments and received feedback from our [community](https://icinga.com/community/) 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. * Single master with clients.
* HA master with clients as command endpoint. * HA master with clients as command endpoint.

View File

@ -849,7 +849,7 @@ negate_arguments | **Optional.** Arguments for the negated command.
### nrpe <a id="plugin-check-command-nrpe"></a> ### 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 server or [NSClient++](https://www.nsclient.org). **Note**: This plugin
is considered insecure/deprecated. is considered insecure/deprecated.

View File

@ -71,7 +71,7 @@ A popular frontend for InfluxDB is for example [Grafana](https://grafana.org).
### Icinga Reporting <a id="addons-visualization-reporting"></a> ### Icinga Reporting <a id="addons-visualization-reporting"></a>
By enabling the [DB IDO](14-features.md#db-ido) feature you can use the 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> ### 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/): Additionally external services can be [integrated with Icinga 2](https://icinga.com/products/integrations/):
* [Pagerduty](https://icinga.com/partners/pagerduty/) * [Pagerduty](https://icinga.com/products/integrations/pagerduty/)
* [VictorOps](https://icinga.com/partners/victorops/) * [VictorOps](https://icinga.com/products/integrations/victorops/)
* [StackStorm](https://icinga.com/partners/stackstorm/) * [StackStorm](https://icinga.com/products/integrations/stackstorm/)
More information can be found on the [Icinga Website](https://icinga.com/). More information can be found on the [Icinga Website](https://icinga.com/).

View File

@ -167,7 +167,7 @@ running Icinga 2.
(gdb) handle SIGPIPE nostop noprint pass (gdb) handle SIGPIPE nostop noprint pass
(gdb) r (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. make sure to attach as much detail as possible.
### GDB Backtrace from Running Process <a id="development-debug-gdb-backtrace-running"></a> ### GDB Backtrace from Running Process <a id="development-debug-gdb-backtrace-running"></a>