Edit a Group’s Configuration¶
You can configure your Ops Manager groups from Ops Manager Settings, which give access to agents, users, roles and group-wide settings.
To modify group-wide settings or view agent information, see the procedures on this page.
To access users and roles, see Manage Ops Manager Users and Roles.
Edit Group Settings¶
To modify group settings, click Settings, then Group Settings.
See Group Settings to view the setting descriptions.
If you have Global Owner access, Ops Manager displays a second Group Settings link under the Admin Only section.
See Admin-Only Group Settings to view the administrative setting descriptions.
Group Settings apply to all the users in the group.
Sets your group’s name.
Only the group’s owner can change the group name.
|Group Time Zone||Sets your group’s time zone.|
|Collect Logs For All Hosts||Activates or deactivates the collection of log data for all hosts. This overwrites the statuses set on the individual hosts.|
|Collect Profiling Information for All Hosts||
Activates or deactivates Ops Manager collection of data from the MongoDB
running on your
When you change this setting, Ops Manager applies the change globally to
To enable the collection of profiling data on a process-by-process basis, see Profile Databases.
When profiling is enabled, Ops Manager collects data from MongoDB’s profiler to provide statistics about performance and database operations. Ensure exposing profile data to Ops Manager is consistent with your information security practices. Also be aware the profiler can consume resources which may adversely affect MongoDB performance.
For more information, see Profile Databases.
|Collect Database Specific Statistics||Allows you to enable or disable the collection of database statistics. For more information, see Profile Databases.|
|Reset Duplicates||Allows you to reset and remove all detected duplicate hosts. This is useful if your server environment has drastically changed and you believe a host is incorrectly marked as a duplicate.|
Allows you to specify resolvable hostnames or IP address for your deployment’s servers. Ops Manager keeps a list of the multiple ways to which each server is referred (hostname, FQDN, IP address) and uses heuristics to determine the best choice. Use this setting to guarantee Ops Manager uses a resolvable method. The method you choose will also be the method used to display the servers in Ops Manager.
To specify a preferred hostname, click Add and do one of the following:
|Suppress Mongos Automatic Discovery||Suppresses automatic discovery of all
|Public Key for SCP Restores||If you use Ops Manager Backup, this setting allows you to generate a public key for SCP backup restoration. If you restore a snapshot through SCP, Ops Manager uses the key to transmit the snapshot. For more information on restores, see how to validate an SCP restore and other SCP FAQs.|
|PagerDuty Service Key||
Sets a default service key for alert notifications sent to a PagerDuty account. Ops Manager enters the key by default when you add a PagerDuty notification to an alert configuration. If you add PagerDuty notifications and if the key used to send the notifications becomes invalid, Ops Manager sends an email to the group owner and eventually removes the key.
You can add PagerDuty notifications only for alerts that require user acknowledgement. Informational alerts, such as the alert that a replica set has elected a new primary, cannot use PagerDuty notification.
Users can acknowledge PagerDuty alert notifications only from the PagerDuty dashboard.
Sets default values for alert notifications sent to Flowdock. Ops Manager enters the values by default when you add a Flowdock notification to an alert configuration. If you add Flowdock notifications, and if credentials to send notifications become invalid, Ops Manager sends an email to the group owner and eventually removes the credentials.
Set the following:
|HipChat Settings||Sets a default room and API token for alert notifications sent to a HipChat account. Ops Manager enters the values by default when you add a HipChat notification to an alert configuration. If you add HipChat notifications and the token used to send notifications becomes invalid, Ops Manager sends an email to the group owner and eventually removes the token.|
Sets a default channel and token for alert notifications sent to a Slack account. You can use either an API token or a Bot token. To create an API token, see the https://api.slack.com/web page in your Slack account. For information on Bot users in Slack, see https://api.slack.com/bot-users.
Ops Manager will enter these values by default when you add a Slack notification to an alert configuration. If add Slack notifications and the token used to send notifications becomes invalid, Ops Manager sends an email to the group owner and eventually removes the token.
Adds a Webhook URL endpoint to which Ops Manager can send alert notifications for programmatic processing. Ops Manager sends an alert notification as an HTTP POST request in which the request body contains a JSON document that uses the same format as the Public API’s Alerts resource.
Ops Manager adds a request header called
If you specify a key in the Webhook Secret field, Ops Manager adds the
To send alert notifications to a Webhook, select the Webhook notification option when creating or editing an alert configuration. If you add a Webhook notification and the URL or optional key becomes invalid, Ops Manager sends an email to the group owner and eventually removes the Webhook settings.
Admin-Only Group Settings¶
The following group settings in the Admin Only section of Settings could, in certain situations, affect more than the group. For example, setting logging to a high verbosity would cause system logs to roll over faster. Only users with the Global Owner role can edit these settings:
|Mongos Deactivation Threshold||Change the amount of time before Ops Manager removes an unreachable
|Monitoring Agent Log Level||Change the verbosity of the Monitoring Agent log.|
|Automation Agent Log Level||Change the verbosity of the Automation Agent log.|
View Agent Status¶
Click Deployment, then the Agents tab, then All Agents. Ops Manager displays the following information about your agents:
|Status||The time of the last ping from the agent.|
|Type||The type of agent.|
|Hostname||The hostname for the agent and any warnings, such as that the agent is down or out-of-date.|
|State||Indicates whether the agent is active.|
|Ping Count||The number of pings (i.e. data payloads) sent by the agent since midnight GMT. Typically agents send pings every minute.|
|Version||The version of the agent software running on this agent instance.|
|Log||Click view logs to view the agent’s log.|