Skip to content

Add a note about not using the operator role for the NOM persistence … #123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 3, 2023
Merged

Add a note about not using the operator role for the NOM persistence … #123

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7481d96
Add a note about not using the operator role for the NOM persistence …
SaschaPeukert Jun 30, 2023
6fc3b58
Update modules/ROOT/pages/addition/instance-requirements.adoc
SaschaPeukert Jun 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions modules/ROOT/pages/addition/instance-requirements.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,11 @@ For the metrics collection feature to work correctly. these configuration values
The agent logs on to the DBMS with the configured user to enable certain features such as viewing relationship and label types, managing privileges, and viewing configuration values.
If you do not want to use the built-in admin user, a role with the minimum set of privileges required for full functionality can be created with:

[NOTE]
====
This role definition can not be used for the user with which the Ops Manager server connects to the persistence database since it has insufficient privileges.
This `operator` role should only be used for the DBMS you want to monitor with an agent.
====

[source, cypher]
----
Expand Down