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 [1] 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 [2] 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:
Right now, at Würth Phoenix, we are investing in automating most of our operations using Ansible. You're probably already familiar with what Ansible does, but to summarize, Ansible is an open-source, command-line IT automation application written in Python. I've talked Read More
We fixed a procmail misconfiguration that was occurring after the upgrade. We updated the following packages: tornado, tornado-autosetup to version 1.32.2-1
We resolved an issue in the neteye update and neteye upgrade commands where the process would halt if the Elasticsearch cluster took longer than 30 seconds to respond to API requests. We updated the following packages: elastic-agent, elastic-agent-autosetup, elastic-agent-neteye-config, elastic-stack-configurator, Read More
We resolved a bug in the nginx configuration for our clickhouse integration. This fix guarantees that queries will no longer be directed to the voting-only node in cluster environments, preventing potential errors. We updated the following packages: clickhouse-neteye-config, clickhouse-neteye-config-autosetup, clickhouse-neteye-config-configurator Read More
We fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade. This enhancement guarantees proper pcs resource management throughout this phase. We updated Read More