Grafana User Management Deprecation in NetEye 4.10
A manual user configuration migration is required before upgrading to 4.10.
Starting in version 4.9, NetEye supports Grafana user management, which is completely integrated into NetEye via its existing roles mechanism. NetEye administrators can create new roles that map to Grafana roles (admin, editor or viewer) at the level of organizations and teams. NetEye users must then be assigned these roles in NetEye’s own module permissions (one NetEye role for each Grafana organization).
The process of changing to this new permissions scheme is not done automatically. Indeed, you can choose the best moment to migrate before an eventual upgrade to NetEye 4.10, when the new permission schema will be mandatory. Before migrating, you will need to prepare by creating roles in NetEye, and assigning organizations and users. You can then mark the checkbox in the Analytics module’s configuration tab to start the migration process. The new scheme will be applied for each user individually when that user logs in for the first time after migration is completed. There is no way to roll back once the whole procedure has been successfully completed.
If you have defined some users and specific roles or teams in Grafana User Management, follow these steps to migrate your configuration:
Check your Grafana configuration
Make sure that “icinga2-influxdb” is added as a data source to your Main Organization (the organization with ID 1)
Log in to NetEye with a Grafana Administrator user.
Go to “ITOA”
Select User >> Switch Current Org (if present) >> Select “Main Org.” :
Go to Configuration >> Data Sources
Icinga2-influxdb should be there:
Make sure that before you configure a NetEye role for an Organization, that Organization has already been added in Grafana.
You can find all existing Grafana Organizations at Server Admin >> Orgs:
Create NetEye roles at Configuration >> Authentication as described in the user guide under Monitoring basics >> User Authentication and Permissions >> Roles
Be completely sure that the organization string matches the Grafana role name (note that there is no string validator) – See  in image below
Make sure that you have replicated exactly the same users/organizations and users/teams relations in the NetEye Analytics permissions configuration
Make sure that the toggle switch View performance Graph in the NetEye role definition is enabled – See  in image below
Finalizing the configuration. Warning: no roll back will be possible after this step.
Enable the flag Apply new permission scheme in the Analytics module configuration tab (Configuration >> Modules >> analytics >> Configuration)
Log out and then log back in so that the necessary changes will take effect
If you need further information, or experience some problem migrating the configuration, feel free to contact our support team using one of the following options:
We fixed a bug in SLM reports for which they were not using the availability information stored in the monitored objects status. So, in case the IDO DB retention policy deleted all the events related to a monitored object, the Read More
We fixed a bug that caused the master to reject the output of the command executed by the command orchestrator module if the executing endpoint did not belong to the target host object zone. For NetEye 4.16 we updated the Read More
We fixed a bug that freezes the UI when a user has a huge services list, and he selects the option to show 500 results per page on the service list view. Also, once update the below packages do a Read More
We have fixed some visual problems in the dashboard panels of the ITOA module. For NetEye 4.16 we updated the following packages: grafana, grafana-autosetup, grafana-neteye-config to version 7.2.0_neteye3.11.1-1
We set the retention of the Icinga2 downtime history to infinite, so that downtimes are never deleted from the Icinga2 IDO. For NetEye 4.16 we updated the following packages: icinga2 to version 2.11.6_neteye1.22.5-1