Update Icinga DB related docs #9423

We are using a central DB-Cluster, therefor Icinga2 got a database on this remote cluster. We used the icinga DB user, created during the step before, to import the DB schema. For this, the additional GRANT options `ALTER` and `CREATE` where needed to install the schema successfully via: ```bash mysql -u icinga -p icinga < /usr/share/icinga2-ido-mysql/schema/mysql.sql ``` Someone may find this a security problem. But I see two benefits: * these GRANT options are only set for the icinga.* database * this setup allows to execute also all later UPGRADE commands as the database user `icinga` - and not as the DB Administrator. Two additional notes: * I also included a small warning about the used default DB password * sadly, I have no way to change this also in the provided mariadb-centos7.png image, so this is left unchanged at the moment

Almost every Icinga 2 node setup requires the Icinga 2 API, as Icinga Web connects to it, Icinga DB requires it, and although it's not clearly mentioned anywhere in the documentation at the moment, it enables the cluster communication functionality.

That's useless.

There is a separate chapter, so why draw attention to installing even more things.

The Icinga DB docs will link to installing Icinga DB Web.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Icinga DB related docs #9423

Update Icinga DB related docs #9423

Commits on Jun 29, 2022