upstream/icingadb-web
1
0
Fork 0
mirror of https://github.com/Icinga/icingadb-web.git synced 2026-05-28 04:36:06 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: Mention the navigation item migration command

Browse source
This commit is contained in:
Johannes Meyer 2021-11-05 13:40:00 +01:00
parent 342ceca676
commit b42a00f76f
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/10-Migration.md
View file

@ -32,7 +32,7 @@ rules. Just copy them over.
![Url Migration Preview](res/url-migration-preview.png)
The dashboard and navigation configuration does not change since these are related
The dashboard and menu item configuration does not change since these are related
to Icinga Web 2. However, if you've used the monitoring module's urls and you want
to update them, this might be straight forward if it's only the url path that needs
to change. Complex filters though can be cumbersome to rewrite.
@ -42,6 +42,16 @@ monitoring module url for which there is a counterpart in Icinga DB Web. You can
switch to the respective view in Icinga DB Web with a single click and either use the
new url from the address bar or add it the usual way to the dashboard and sidebar.
Host and service actions on the other hand are part of the monitoring module. For them
Icinga DB Web provides their own counterparts. You don't need to migrate them manually
though. The `migrate` command of Icinga Web 2 (>= v2.9.4) provides an action for that:
`icingacli migrate navigation [--user=<username>] [--delete]`
By default this will migrate the configuration of all users and won't delete the old
ones. It can be restricted to a single user and the removal of the old configuration
can be enabled as well.
### Automation
For those who have a plethora of custom dashboards or navigation items there is also