Merge pull request #7504 from Icinga/feature/docs-last-bits-for-2-11
Docs: Update product URLs and missing bits
27
README.md
|
@ -16,25 +16,33 @@
|
|||
|
||||
## About
|
||||
|
||||
[Icinga 2](https://icinga.com/products/icinga-2/) is a monitoring system which checks
|
||||
[Icinga](https://icinga.com/products/) is a monitoring system which checks
|
||||
the availability of your network resources, notifies users of outages, and generates
|
||||
performance data for reporting.
|
||||
|
||||
Scalable and extensible, Icinga 2 can monitor large, complex environments across
|
||||
Scalable and extensible, Icinga can monitor large, complex environments across
|
||||
multiple locations.
|
||||
|
||||
Icinga 2 as core requires [Icinga Web 2](https://icinga.com/products/icinga-web-2/)
|
||||
on top in your Icinga Stack.
|
||||
Icinga 2 is the monitoring server and requires [Icinga Web 2](https://icinga.com/products/)
|
||||
on top in your Icinga Stack. The [configuration](https://icinga.com/products/configuration/)
|
||||
can be easily managed with either the [Icinga Director](https://icinga.com/docs/director/latest/),
|
||||
config management tools or plain text within the [Icinga DSL](https://icinga.com/docs/icinga2/latest/doc/17-language-reference/).
|
||||
|
||||
![Icinga Dashboard](https://icinga.com/wp-content/uploads/2017/12/icingaweb2-2.5.0-dashboard.png)
|
||||
|
||||
## Installation
|
||||
|
||||
For installing Icinga please check the [installation chapter](https://icinga.com/docs/icinga2/latest/doc/02-getting-started/)
|
||||
in the documentation.
|
||||
* [Installation](https://icinga.com/docs/icinga2/latest/doc/02-installation/)
|
||||
* [Monitoring Basics](https://icinga.com/docs/icinga2/latest/doc/03-monitoring-basics/)
|
||||
* [Configuration](https://icinga.com/docs/icinga2/latest/doc/04-configuration/)
|
||||
* [Distributed Monitoring](https://icinga.com/docs/icinga2/latest/doc/06-distributed-monitoring/)
|
||||
* [Addons, Integrations and Features](https://icinga.com/docs/icinga2/latest/doc/13-addons/)
|
||||
* [Troubleshooting](https://icinga.com/docs/icinga2/latest/doc/15-troubleshooting/)
|
||||
* [Upgrading](https://icinga.com/docs/icinga2/latest/doc/16-upgrading-icinga-2/)
|
||||
|
||||
If you are a packager, please read the [development chapter](https://icinga.com/docs/icinga2/latest/doc/21-development/)
|
||||
for more details.
|
||||
Once Icinga Server and Web are running in your distributed environment,
|
||||
make sure to check out the many [Icinga modules](https://icinga.com/docs/)
|
||||
for even better monitoring.
|
||||
|
||||
## Documentation
|
||||
|
||||
|
@ -74,6 +82,9 @@ contribution is appreciated!
|
|||
|
||||
Please continue reading in the [contributing chapter](CONTRIBUTING.md).
|
||||
|
||||
If you are a packager, please read the [development chapter](https://icinga.com/docs/icinga2/latest/doc/21-development/)
|
||||
for more details.
|
||||
|
||||
### Security Issues
|
||||
|
||||
For reporting security issues please visit [this page](https://icinga.com/contact/security/).
|
||||
|
|
|
@ -2,15 +2,17 @@
|
|||
|
||||
## What is Icinga 2? <a id="what-is-icinga2"></a>
|
||||
|
||||
[Icinga 2](https://icinga.com/products/icinga-2/) is a monitoring system which checks
|
||||
[Icinga](https://icinga.com/products/) is a monitoring system which checks
|
||||
the availability of your network resources, notifies users of outages, and generates
|
||||
performance data for reporting.
|
||||
|
||||
Scalable and extensible, Icinga 2 can monitor large, complex environments across
|
||||
Scalable and extensible, Icinga can monitor large, complex environments across
|
||||
multiple locations.
|
||||
|
||||
Icinga 2 as core requires [Icinga Web 2](https://icinga.com/products/icinga-web-2/)
|
||||
on top in your Icinga Stack.
|
||||
Icinga 2 is the monitoring server and requires [Icinga Web 2](https://icinga.com/products/)
|
||||
on top in your Icinga Stack. The [configuration](https://icinga.com/products/configuration/)
|
||||
can be easily managed with either the [Icinga Director](https://icinga.com/docs/director/latest/),
|
||||
config management tools or plain text within the [Icinga DSL](04-configuration.md#configuration).
|
||||
|
||||
|
||||
![Icinga 2 Distributed Master and Satellites with Agents](images/distributed-monitoring/icinga2_distributed_monitoring_scenarios_master_satellites_agents.png)
|
||||
|
@ -25,7 +27,7 @@ on top in your Icinga Stack.
|
|||
* [Troubleshooting](15-troubleshooting.md#troubleshooting)
|
||||
* [Upgrading](16-upgrading-icinga-2.md#upgrading-icinga-2)
|
||||
|
||||
Once Icinga Core and Web are running in your distributed environment,
|
||||
Once Icinga Server and Web are running in your distributed environment,
|
||||
make sure to check out the many [Icinga modules](https://icinga.com/docs/)
|
||||
for even better monitoring.
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ First off you have to install Icinga 2. The preferred way of doing this
|
|||
is to use the official package repositories depending on which operating system
|
||||
and distribution you are running.
|
||||
|
||||
Official repositories ([support matrix](https://icinga.com/support/details/)):
|
||||
Official repositories ([support matrix](https://icinga.com/subscription/support-details/)):
|
||||
|
||||
Distribution | Repository
|
||||
------------------------|---------------------------
|
||||
|
@ -549,7 +549,7 @@ Test it:
|
|||
# vim /etc/icinga2/conf.d/templates.conf
|
||||
```
|
||||
|
||||
![Vim with syntax highlighting](images/getting-started/vim-syntax.png "Vim with Icinga 2 syntax highlighting")
|
||||
![Vim with syntax highlighting](images/installation/vim-syntax.png "Vim with Icinga 2 syntax highlighting")
|
||||
|
||||
|
||||
### Configuration Syntax Highlighting using Nano <a id="configuration-syntax-highlighting-nano"></a>
|
||||
|
@ -593,7 +593,7 @@ Test it:
|
|||
$ nano /etc/icinga2/conf.d/templates.conf
|
||||
```
|
||||
|
||||
![Nano with syntax highlighting](images/getting-started/nano-syntax.png "Nano with Icinga 2 syntax highlighting")
|
||||
![Nano with syntax highlighting](images/installation/nano-syntax.png "Nano with Icinga 2 syntax highlighting")
|
||||
|
||||
## Setting up Icinga Web 2 <a id="setting-up-icingaweb2"></a>
|
||||
|
||||
|
@ -704,7 +704,7 @@ GRANT SELECT, INSERT, UPDATE, DELETE, DROP, CREATE VIEW, INDEX, EXECUTE ON icing
|
|||
quit
|
||||
```
|
||||
|
||||
![setting up the database on CentOS 7](images/getting-started/mariadb-centos7.png "Setting up the database on CentOS 7")
|
||||
![setting up the database on CentOS 7](images/installation/mariadb-centos7.png "Setting up the database on CentOS 7")
|
||||
|
||||
After creating the database you can import the Icinga 2 IDO schema using the
|
||||
following command. Enter the root password into the prompt when asked.
|
||||
|
@ -876,7 +876,7 @@ export PGPASSWORD=icinga
|
|||
psql -U icinga -d icinga < /usr/share/icinga2-ido-pgsql/schema/pgsql.sql
|
||||
```
|
||||
|
||||
![importing the Icinga 2 IDO schema](images/getting-started/postgr-import-ido.png "Importing the Icinga 2 IDO schema on Debian Jessie")
|
||||
![importing the Icinga 2 IDO schema](images/installation/postgr-import-ido.png "Importing the Icinga 2 IDO schema on Debian Jessie")
|
||||
|
||||
|
||||
#### Enabling the IDO PostgreSQL module <a id="enabling-ido-postgresql"></a>
|
||||
|
|
|
@ -1,8 +1,18 @@
|
|||
# Configuration: First Steps <a id="configuration"></a>
|
||||
# Configuration <a id="configuration"></a>
|
||||
|
||||
This chapter provides an introduction into best practices for your Icinga 2 configuration.
|
||||
The configuration files which are automatically created when installing the Icinga 2 packages
|
||||
are a good way to start with Icinga 2.
|
||||
The Icinga [configuration](https://icinga.com/products/configuration/)
|
||||
can be easily managed with either the [Icinga Director](https://icinga.com/docs/director/latest/),
|
||||
config management tools or plain text within the [Icinga DSL](04-configuration.md#configuration).
|
||||
|
||||
Before looking into web based configuration or any sort of automation,
|
||||
we recommend to start with the configuration files and fully understand
|
||||
the possibilities of the Icinga DSL (Domain Specific Language).
|
||||
|
||||
The package installation provides example configuration which already
|
||||
monitors the local Icinga server. You can view the monitoring details
|
||||
in Icinga Web.
|
||||
|
||||
![Icinga Web Local Server](images/configuration/icinga_web_local_server.png)
|
||||
|
||||
The [Language Reference](17-language-reference.md#language-reference) chapter explains details
|
||||
on value types (string, number, dictionaries, etc.) and the general configuration syntax.
|
||||
|
@ -15,8 +25,9 @@ decide for a possible strategy.
|
|||
|
||||
There are many ways of creating Icinga 2 configuration objects:
|
||||
|
||||
* The [Icinga Director](https://icinga.com/docs/director/latest/) as web based and/or automation configuration interface
|
||||
* [Monitoring Automation with Icinga - The Director](https://icinga.com/2019/04/23/monitoring-automation-with-icinga-the-director/)
|
||||
* Manually with your preferred editor, for example vi(m), nano, notepad, etc.
|
||||
* A configuration tool for Icinga 2 e.g. the [Icinga Director](https://github.com/Icinga/icingaweb2-module-director)
|
||||
* Generated by a [configuration management tool](13-addons.md#configuration-tools) such as Puppet, Chef, Ansible, etc.
|
||||
* A custom exporter script from your CMDB or inventory tool
|
||||
* etc.
|
||||
|
@ -66,7 +77,7 @@ There is a detailed chapter on [distributed monitoring scenarios](06-distributed
|
|||
Please ensure to have read the [introduction](06-distributed-monitoring.md#distributed-monitoring) at first glance.
|
||||
|
||||
If you happen to have further questions, do not hesitate to join the
|
||||
[community support channels](https://icinga.com/community/)
|
||||
[community forum](https://community.icinga.com)
|
||||
and ask community members for their experience and best practices.
|
||||
|
||||
## Your Configuration <a id="your-configuration"></a>
|
||||
|
@ -86,7 +97,7 @@ in your icinga2.conf file.
|
|||
include_recursive "objects.d"
|
||||
```
|
||||
|
||||
This approach is used by the [Icinga 2 Puppet module](https://github.com/Icinga/puppet-icinga2).
|
||||
This approach is used by the [Icinga 2 Puppet module](https://icinga.com/products/integrations/puppet/).
|
||||
|
||||
If you plan to setup a distributed setup with HA clusters and clients, please refer to [this chapter](#06-distributed-monitoring.md#distributed-monitoring-top-down)
|
||||
for examples with `zones.d` as configuration directory.
|
||||
|
@ -216,7 +227,8 @@ const TicketSalt = ""
|
|||
```
|
||||
|
||||
The `ZoneName` and `TicketSalt` constants are required for remote client
|
||||
and distributed setups only.
|
||||
and distributed setups. The `node setup/wizard` CLI tools take care of
|
||||
populating these values.
|
||||
|
||||
### zones.conf <a id="zones-conf"></a>
|
||||
|
||||
|
|
|
@ -910,6 +910,8 @@ Instead, choose a plugin and configure its parameters and thresholds. The follow
|
|||
* [kdc](10-icinga-template-library.md#plugin-contrib-command-kdc)
|
||||
* [rbl](10-icinga-template-library.md#plugin-contrib-command-rbl)
|
||||
|
||||
* [Icinga Certificate Monitoring](https://icinga.com/products/icinga-certificate-monitoring/)
|
||||
|
||||
### Java Monitoring <a id="service-monitoring-java"></a>
|
||||
|
||||
* [jmx4perl](10-icinga-template-library.md#plugin-contrib-command-jmx4perl)
|
||||
|
@ -934,6 +936,7 @@ Instead, choose a plugin and configure its parameters and thresholds. The follow
|
|||
|
||||
### VMware Monitoring <a id="service-monitoring-virtualization-vmware"></a>
|
||||
|
||||
* [Icinga Module for vSphere](https://icinga.com/products/icinga-module-for-vsphere/)
|
||||
* [esxi_hardware](10-icinga-template-library.md#plugin-contrib-command-esxi-hardware)
|
||||
* [VMware](10-icinga-template-library.md#plugin-contrib-vmware)
|
||||
|
||||
|
|
|
@ -959,9 +959,9 @@ can start with additional integrations to manage and deploy your
|
|||
configuration:
|
||||
|
||||
* [Icinga Director](https://icinga.com/docs/director/latest/) provides a web interface to manage configuration and also allows to sync imported resources (CMDB, PuppetDB, etc.)
|
||||
* [Ansible Roles](https://github.com/Icinga/icinga2-ansible)
|
||||
* [Puppet Module](https://github.com/Icinga/puppet-icinga2)
|
||||
* [Chef Cookbook](https://github.com/Icinga/chef-icinga2)
|
||||
* [Ansible Roles](https://icinga.com/products/integrations/)
|
||||
* [Puppet Module](https://icinga.com/products/integrations/puppet/)
|
||||
* [Chef Cookbook](https://icinga.com/products/integrations/chef/)
|
||||
|
||||
More details can be found [here](13-addons.md#configuration-tools).
|
||||
|
||||
|
|
116
doc/13-addons.md
|
@ -1,6 +1,27 @@
|
|||
# Icinga 2 Addons <a id="addons"></a>
|
||||
# Icinga 2 Addons and Integrations <a id="addons"></a>
|
||||
|
||||
## Graphing <a id="addons-graphing"></a>
|
||||
For an uptodate overview of all integrations and modules,
|
||||
please visit [https://icinga.com/products/](https://icinga.com/products/).
|
||||
|
||||
|
||||
## Icinga Reporting <a id="addons-reporting"></a>
|
||||
|
||||
The [Icinga Reporting Module](https://icinga.com/docs/reporting/latest/)
|
||||
is the framework and foundation we created to handle data collected
|
||||
by Icinga 2 and other data providers. By definition Icinga Reporting does not collect
|
||||
or calculate any data. The framework processes usable data from data providers such as
|
||||
Icinga’s IDO or Icinga Web 2 modules and makes them available in different formats.
|
||||
|
||||
It can display the data directly within the Icinga web interface or export it to PDF,
|
||||
JSON or CSV format. With scheduled reports you can receive the prepared data periodically
|
||||
via email.
|
||||
|
||||
![Icinga Reporting](images/addons/icinga_reporting.png)
|
||||
|
||||
Follow along in this [hands-on blog post](https://icinga.com/2019/06/17/icinga-reporting-hands-on/).
|
||||
|
||||
|
||||
## Graphs and Metrics <a id="addons-graphs-metrics"></a>
|
||||
|
||||
### Graphite <a id="addons-graphing-graphite"></a>
|
||||
|
||||
|
@ -95,6 +116,27 @@ installation, configuration and integration.
|
|||
|
||||
![Icinga Web 2 Maps](images/addons/icingaweb2_maps.png)
|
||||
|
||||
### Business Process <a id="addons-business-process"></a>
|
||||
|
||||
Create top-level views of your applications in a graphical editor.
|
||||
Rules express dependencies between existing hosts and services and
|
||||
let you alert on application level. Business processes are displayed
|
||||
in a tree or list overview and can be added to any dashboard.
|
||||
|
||||
![Icinga Web 2 Business Process](images/addons/icingaweb2_businessprocess.png)
|
||||
|
||||
Read more [here](https://icinga.com/products/icinga-business-process-modelling/).
|
||||
|
||||
### Certificate Monitoring <a id="addons-visualization-certificate-monitoring"></a>
|
||||
|
||||
Monitor your certificates in an efficient and comfortable way. Be aware of required
|
||||
actions and view all details at a glance.
|
||||
|
||||
![Icinga Certificate Monitoring](images/addons/icinga_certificate_monitoring.png)
|
||||
|
||||
Read more [here](https://icinga.com/products/icinga-certificate-monitoring/)
|
||||
and [here](https://icinga.com/2019/06/03/monitoring-automation-with-icinga-certificate-monitoring/).
|
||||
|
||||
### Dashing Dashboard <a id="addons-visualization-dashing-dashboard"></a>
|
||||
|
||||
The [Icinga 2 dashboard](https://github.com/dnsmichi/dashing-icinga2) is built
|
||||
|
@ -107,40 +149,6 @@ host and service problem lists as Iframe.
|
|||
|
||||
![Dashing dashboard](images/addons/dashing_icinga2.png)
|
||||
|
||||
### Business Process <a id="addons-business-process"></a>
|
||||
|
||||
Create top-level views of your applications in a graphical editor.
|
||||
Rules express dependencies between existing hosts and services and
|
||||
let you alert on application level. Business processes are displayed
|
||||
in a tree or list overview and can be added to any dashboard.
|
||||
|
||||
![Icinga Web 2 Business Process](images/addons/icingaweb2_businessprocess.png)
|
||||
|
||||
### NagVis <a id="addons-visualization-nagvis"></a>
|
||||
|
||||
By using the [DB IDO](14-features.md#db-ido) feature
|
||||
you can create your own network maps
|
||||
based on your monitoring configuration and status data using [NagVis](https://www.nagvis.org).
|
||||
|
||||
The configuration in nagvis.ini.php should look like this for Livestatus for example:
|
||||
|
||||
```
|
||||
[backend_live_1]
|
||||
backendtype="mklivestatus"
|
||||
socket="unix:/var/run/icinga2/cmd/livestatus"
|
||||
```
|
||||
|
||||
If you are planning an integration into Icinga Web 2, look at [this module](https://github.com/Icinga/icingaweb2-module-nagvis).
|
||||
|
||||
### 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://icinga.com/docs/icinga1/latest/en/reporting.html).
|
||||
|
||||
### Thruk <a id="addons-visualization-thruk"></a>
|
||||
|
||||
[Thruk](https://www.thruk.org) is an alternative web interface which can be used with Icinga 2
|
||||
and the [Livestatus](14-features.md#setting-up-livestatus) feature.
|
||||
|
||||
## Log Monitoring <a id="log-monitoring"></a>
|
||||
|
||||
|
@ -166,6 +174,10 @@ There's a variety of resources available, for example different notification scr
|
|||
* Ticket systems
|
||||
* etc.
|
||||
|
||||
Blog posts and howtos:
|
||||
|
||||
* [Environmental Monitoring and Alerting](https://icinga.com/2019/09/02/environmental-monitoring-and-alerting-via-text-message/)
|
||||
|
||||
Additionally external services can be [integrated with Icinga 2](https://icinga.com/products/integrations/):
|
||||
|
||||
* [Pagerduty](https://icinga.com/products/integrations/pagerduty/)
|
||||
|
@ -176,33 +188,13 @@ More information can be found on the [Icinga Website](https://icinga.com/).
|
|||
|
||||
## Configuration Management Tools <a id="configuration-tools"></a>
|
||||
|
||||
If you require your favourite configuration tool to export the Icinga 2 configuration, please get in
|
||||
touch with their developers. The Icinga project does not provide a configuration web interface
|
||||
yet. Follow the [Icinga Blog](https://icinga.com/blog/) for updates on this topic.
|
||||
Checkout these specific integrations:
|
||||
|
||||
If you're looking for puppet manifests, chef cookbooks, ansible recipes, etc. -- we're happy
|
||||
to integrate them upstream, so please get in touch with the [Icinga team](https://icinga.com/community/).
|
||||
* [Ansible Roles](https://icinga.com/products/integrations/)
|
||||
* [Puppet Module](https://icinga.com/products/integrations/puppet/)
|
||||
* [Chef Cookbook](https://icinga.com/products/integrations/chef/)
|
||||
|
||||
These tools are currently in development and require feedback and tests:
|
||||
If you're looking for different config management integrations -- we're happy
|
||||
to add them upstream, so please get in touch with the [Icinga team](https://icinga.com/community/).
|
||||
|
||||
* [Ansible Roles](https://github.com/Icinga/icinga2-ansible)
|
||||
* [Puppet Module](https://github.com/Icinga/puppet-icinga2)
|
||||
* [Chef Cookbook](https://github.com/Icinga/chef-icinga2)
|
||||
|
||||
## More Addon Integration Hints <a id="addon-integration-hints"></a>
|
||||
|
||||
### PNP Action Url <a id="addons-graphing-pnp-action-url"></a>
|
||||
|
||||
They work in a similar fashion for Icinga 2 and are used for 1.x web interfaces (Icinga Web 2 doesn't require
|
||||
the action url attribute in its own module).
|
||||
|
||||
```
|
||||
template Host "pnp-hst" {
|
||||
action_url = "/pnp4nagios/graph?host=$HOSTNAME$"
|
||||
}
|
||||
|
||||
template Service "pnp-svc" {
|
||||
action_url = "/pnp4nagios/graph?host=$HOSTNAME$&srv=$SERVICEDESC$"
|
||||
}
|
||||
```
|
||||
|
||||
|
|
|
@ -225,7 +225,7 @@ expects the Graphite Carbon Cache to listen at `127.0.0.1` on TCP port `2003`.
|
|||
|
||||
#### Graphite Schema <a id="graphite-carbon-cache-writer-schema"></a>
|
||||
|
||||
The current naming schema is defined as follows. The [Icinga Web 2 Graphite module](https://github.com/icinga/icingaweb2-module-graphite)
|
||||
The current naming schema is defined as follows. The [Icinga Web 2 Graphite module](https://icinga.com/products/integrations/graphite/)
|
||||
depends on this schema.
|
||||
|
||||
The default prefix for hosts and services is configured using
|
||||
|
@ -438,14 +438,14 @@ where the InfluxDB HTTP API or Telegraf as Proxy are running.
|
|||
|
||||
### Elastic Stack Integration <a id="elastic-stack-integration"></a>
|
||||
|
||||
[Icingabeat](https://github.com/icinga/icingabeat) is an Elastic Beat that fetches data
|
||||
[Icingabeat](https://icinga.com/products/integrations/elastic/) is an Elastic Beat that fetches data
|
||||
from the Icinga 2 API and sends it either directly to [Elasticsearch](https://www.elastic.co/products/elasticsearch)
|
||||
or [Logstash](https://www.elastic.co/products/logstash).
|
||||
|
||||
More integrations:
|
||||
|
||||
* [Logstash output](https://github.com/Icinga/logstash-output-icinga) for the Icinga 2 API.
|
||||
* [Logstash Grok Pattern](https://github.com/Icinga/logstash-grok-pattern) for Icinga 2 logs.
|
||||
* [Logstash output](https://icinga.com/products/integrations/elastic/) for the Icinga 2 API.
|
||||
* [Logstash Grok Pattern](https://icinga.com/products/integrations/elastic/) for Icinga 2 logs.
|
||||
|
||||
#### Elasticsearch Writer <a id="elasticsearch-writer"></a>
|
||||
|
||||
|
|
|
@ -6,6 +6,33 @@ The Icinga 2 configuration format introduces plenty of behavioural changes. In
|
|||
order to ease migration from Icinga 1.x, this section provides hints and tips
|
||||
on your migration requirements.
|
||||
|
||||
|
||||
### Automated Config Migration <a id="automated-config-migration"></a>
|
||||
|
||||
Depending on your previous setup, you may have already used different sources
|
||||
for generating the 1.x configuration files. If this is the case,
|
||||
we strongly recommend to use these sources in combination with
|
||||
the [Icinga Director](https://icinga.com/docs/director/latest/doc/01-Introduction/).
|
||||
|
||||
This can be for example:
|
||||
|
||||
* A CMDB or RDBMS which provides host details and facts
|
||||
* PuppetDB
|
||||
* CSV/XSL/JSON files
|
||||
* Cloud resources (AWS, etc.)
|
||||
|
||||
In case you have been using Icinga Web 1.x or an addon requiring
|
||||
the underlying IDO database, you can use this as database resource
|
||||
to import the host details.
|
||||
|
||||
Talks:
|
||||
|
||||
* [This talk from OSMC 2016](https://www.youtube.com/watch?v=T6GBsfeXIZI) shares more insights (German).
|
||||
* [Automated Monitoring in heterogeneous environments](https://www.youtube.com/watch?v=bkUlS5rlHzM&list=PLeoxx10paaAn_xHJ5wBhnBJyW_d5G7-Bl&index=8)
|
||||
|
||||
Continue reading more about [Import Sources](https://icinga.com/docs/director/latest/doc/70-Import-and-Sync/)
|
||||
for the Icinga Director.
|
||||
|
||||
### Manual Config Migration <a id="manual-config-migration"></a>
|
||||
|
||||
For a long-term migration of your configuration you should consider re-creating
|
||||
|
|
After Width: | Height: | Size: 246 KiB |
After Width: | Height: | Size: 306 KiB |
After Width: | Height: | Size: 296 KiB |
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 50 KiB |
Before Width: | Height: | Size: 48 KiB After Width: | Height: | Size: 48 KiB |
Before Width: | Height: | Size: 32 KiB After Width: | Height: | Size: 32 KiB |
Before Width: | Height: | Size: 38 KiB After Width: | Height: | Size: 38 KiB |
|
@ -3,9 +3,9 @@ docs_dir: doc
|
|||
dev_addr: 0.0.0.0:8000
|
||||
pages:
|
||||
- 'About Icinga 2': '01-about.md'
|
||||
- 'Getting Started': '02-getting-started.md'
|
||||
- 'Installation': '02-installation.md'
|
||||
- 'Monitoring Basics': '03-monitoring-basics.md'
|
||||
- 'Configuring Icinga 2': '04-configuring-icinga-2.md'
|
||||
- 'Configuration': '04-configuration.md'
|
||||
- 'Service Monitoring': '05-service-monitoring.md'
|
||||
- 'Distributed Monitoring': '06-distributed-monitoring.md'
|
||||
- 'Agent Based Monitoring': '07-agent-based-monitoring.md'
|
||||
|
|