You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There are various places in Icinga Web where urls or filters of specific products are referenced. One such product is the monitoring module as well as Icinga DB Web.
The various places
Dashboards
Navigation Items
Restrictions
The Problem
Users may have plenty of custom dashboards, navigation items as well as plenty of roles with restrictions. They either reference specific monitoring urls with filters or icingadb urls with wildcards in filters which still use the equal/unequal operators.
Dashboards
No url migration
Users have no automated way of migrating dashboard urls at the moment.
Navigation Items
Possibly no wildcard filter migration
While navigation items can already be migrated by using icingacli migrate navigation, we have to verify that wildcard filters are also migrated.
Restrictions
No filter migration at all
Users have no automated way of migrating monitoring restrictions to icingadb and icingadb wildcard filters.
Describe the solution you'd like
Dashboards
There should be a new command icingacli migrate monitoring-dashboards (Why monitoring-? Because I don't want to waste the dashboards command), which migrates monitoring-dasboard-urls to their new icingadb counterparts.
There should be a new command icingacli migrate icingadb-dashboards which migrates icingadb-dashboard-urls which use the old wildcard filter syntax.
Navigation Items
Users who already ran the migration in the past, should be able to run it again to migrate the wildcard filters.
Restrictions
There should be a new command icingacli migrate monitoring-restrictions which migrates monitoring restrictions to their new icingadb counterparts.
There should be a new command icingacli migrate icingadb-restrictions which migrates icingadb restrictions which use the old wildcard filter syntax.
Additional context
The migration of urls and filters is already possible by using Icinga\Module\Icingadb\Compat\UrlMigrator. The only thing that needs to be implemented are the commands and the configuration handling.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There are various places in Icinga Web where urls or filters of specific products are referenced. One such product is the monitoring module as well as Icinga DB Web.
The various places
The Problem
Users may have plenty of custom dashboards, navigation items as well as plenty of roles with restrictions. They either reference specific monitoring urls with filters or icingadb urls with wildcards in filters which still use the equal/unequal operators.
Dashboards
Users have no automated way of migrating dashboard urls at the moment.
Navigation Items
While navigation items can already be migrated by using
icingacli migrate navigation
, we have to verify that wildcard filters are also migrated.Restrictions
Users have no automated way of migrating monitoring restrictions to icingadb and icingadb wildcard filters.
Describe the solution you'd like
Dashboards
There should be a new command
icingacli migrate monitoring-dashboards
(Whymonitoring-
? Because I don't want to waste thedashboards
command), which migrates monitoring-dasboard-urls to their new icingadb counterparts.There should be a new command
icingacli migrate icingadb-dashboards
which migrates icingadb-dashboard-urls which use the old wildcard filter syntax.Navigation Items
Users who already ran the migration in the past, should be able to run it again to migrate the wildcard filters.
Restrictions
There should be a new command
icingacli migrate monitoring-restrictions
which migrates monitoring restrictions to their new icingadb counterparts.There should be a new command
icingacli migrate icingadb-restrictions
which migrates icingadb restrictions which use the old wildcard filter syntax.Additional context
The migration of urls and filters is already possible by using
Icinga\Module\Icingadb\Compat\UrlMigrator
. The only thing that needs to be implemented are the commands and the configuration handling.The text was updated successfully, but these errors were encountered: