Navigation

Edit Project Settings

Overview

You can configure project-specific settings from the project’s Settings page.

Edit Project Settings

To modify project settings, select the project in the Context and click Settings.

The Project Settings displays the configurable settings. See Project Settings to view the setting descriptions.

Project Settings

Project Settings apply to all the users in the project.

Setting Description
Project

Sets your project’s name.

Note

Only a user with the project Owner access for the project can edit the project name.

Project Time Zone Sets your project’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 Cloud Manager collection of data from the MongoDB database profilers running on your mongod instances. A mongod instance must have its profiler enabled in order for Cloud Manager to collect data from it.

When you change this setting, Cloud Manager applies the change globally to all mongod processes in the project. For example, if you disable this setting, Cloud Manager disables the collection of profiling data for all the project’s processes. This setting does not affect whether the profiler is enabled on a given mongod process, only whether Cloud Manager collects profiling data.

To enable the collection of profiling data on a process-by-process basis, see Profile Databases.

When profiling is enabled, Cloud Manager collects data from MongoDB’s profiler to provide statistics about performance and database operations. Ensure exposing profile data to Cloud 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.
Preferred Hostnames

Allows you to specify resolvable hostnames or IP address for your deployment’s servers. Cloud 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 Cloud Manager uses a resolvable method. The method you choose will also be the method used to display the servers in Cloud Manager.

To specify a preferred hostname, click Add and do one of the following:

  • To specify hostnames that end with a particular string, click the Ends With button and enter the string.

  • To specify hostnames that match a pattern, click the Regex button and enter a regular expression. An expression that uses “starts with” behavior must have .* at the end in order to correctly match. For example, to specify hostnames that start with acme-, enter:

    ^acme-.*
    
Suppress Mongos Automatic Discovery Suppresses automatic discovery of all mongos processes in your deployment’s sharded clusters.
Public Key for SCP Restores If you use Cloud Manager Backup, this setting allows you to generate a public key for SCP backup restoration. If you restore a snapshot through SCP, Cloud 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. Cloud 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, Cloud Manager sends an email to the project 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.

Flowdock Settings

Sets default values for alert notifications sent to Flowdock. Cloud 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, Cloud Manager sends an email to the project owner and eventually removes the credentials.

Set the following:

  • Org Name: The Flowdock organization name in lower-case letters. This is the name that appears after www.flowdock.com/app/ in the URL string.
  • Flow Name: The flow name in lower-case letters. The flow name appears after the org name in the URL string: www.flowdock.com/app/<org-name>/<flow-name>.
  • API Token: Your Flowdock “personal API token” found on the https://www.flowdock.com/account/tokens page of your Flowdock account.
HipChat Settings Sets a default room and API token for alert notifications sent to a HipChat account. Cloud 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, Cloud Manager sends an email to the project owner and eventually removes the token.
Slack Settings

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.

Cloud 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, Cloud Manager sends an email to the project owner and eventually removes the token.

Webhook Settings

Adds a Webhook URL endpoint to which Cloud Manager can send alert notifications for programmatic processing. Cloud 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.

Cloud Manager adds a request header called X-MMS-Event to distinguish between various alert states. The possible values for this header are:

alert.open The alert was just opened.
alert.close The alert was resolved.
alert.update A previously opened alert is still open.
alert.acknowledge The alert was acknowledged.
alert.cancel The alert became invalid and was canceled.
alert.inform Represents an informational alert, which is a point-in-time event, such as “Primary Elected.”

If you specify a key in the Webhook Secret field, Cloud Manager adds the X-MMS-Signature request header, which contains the hex-encoded HMAC signature of the request body. The signature is created using the provided secret.

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, Cloud Manager sends an email to the project owner and eventually removes the Webhook settings.

Note

The CIDR address blocks provided in Backup SCP Restores are also used for the Webhooks. You must allow HTTP traffic from those CIDR address blocks.