A user with the required privileges and the same name and password pair as provided in the agent properties must be created on the admin database of every instance that is to be monitored. For a replica set it is sufficient to create the user on the instance that will be directly monitored. For a sharded replica set with cluster discovery enabled, the user must be created through one of the mongos query servers for the main data collection as well as on every mongod data and config server since each server will be contacted directly for reliable availability monitoring. If the user is missing on one or more of mongod instances, the agent will start and operate normally except for the availability collections for those individual servers. Any such failures will be written to the agent log.
User and role collection will require the database client user to have additional privileges. If the privilege check fails, the agent will log the insufficient privileges at the WARN level and proceed with all other data collection as usual. If user and role dashboard isn't showing any data, consult the agent log and check the database client user’s privileges in the mongo shell.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center