API >
API Resources >
Clusters >
Get Advanced Configuration Options for One Cluster

Get Advanced Configuration Options for One Cluster¶

On this page

Syntax
HTTP Response Elements
Example
- Request
- Response

Note

This feature is not available for M0 (Free Tier), M2, and M5 clusters. For more information, see Atlas M0 (Free Tier), M2, and M5 Limitations.

Note

Groups and projects are synonymous terms. Your {GROUP-ID} is the same as your project ID. For existing groups, your group/project ID remains the same. The resource and corresponding endpoints use the term groups.

The Atlas API uses HTTP Digest Authentication. Provide your Atlas username and API key as the username and password when constructing the HTTP request.

For complete documentation on configuring API access for an Atlas project, see Configure Atlas API Access.

Base URL: https://cloud.mongodb.com/api/atlas/v1.0

Syntax¶

copy

GET /groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/processArgs

Request Path Parameters¶

Path Element	Required/Optional	Description
`GROUP-ID`	Required.	The unique identifier for the project containing the cluster you want to retrieve.
`CLUSTER-NAME`	Required	The name of the cluster to retrieve.

Request Query Parameters¶

This endpoint may use any of the HTTP request query parameters available to all Atlas API resources. These are all optional.

Name	Type	Description	Default
`pretty`	boolean	Display response in a prettyprint format.	`false`
`envelope`	boolean	Specifies whether or not to wrap the response in an envelope.	`false`

Request Body Parameters¶

This endpoint does not use HTTP request body parameters.

HTTP Response Elements¶

Name	Type	Description
`failIndexKeyTooLong`	boolean	When `true`, documents can only be updated or inserted if, for all indexed fields on the target collection, the corresponding index entries do not exceed 1024 bytes. When `false`, `mongod` writes documents that breach the limit but does not index them. This option corresponds to the `failIndexKeyTooLong` `mongod` parameter.
`javascriptEnabled`	boolean	When `true`, the cluster allows execution of operations that perform server-side executions of JavaScript. When `false`, the cluster disables execution of those operations. This option corresponds to the `security.javascriptEnabled` `mongod` configuration file option.
`minimumEnabledTlsProtocol`	string	The minimum Transport Layer Security (TLS) version the cluster accepts for incoming connections. Clusters using the deprecated TLS 1.0 protocol version should consider setting TLS 1.1 or later as the minimum TLS protocol version. To learn more about TLS 1.0 deprecation, see What versions of TLS does Atlas support?. This option corresponds to the `net.ssl.disabledProtocols` `mongod` configuration file option.
`noTableScan`	boolean	When `true`, the cluster disables the execution of any query that requires a collection scan to return results. When `false`, the cluster allows the execution of those operations. This option corresponds to the `notablescan` `mongod` parameter.
`oplogSizeMB`	integer	The custom oplog size of the cluster. A value of `null` indicates that the cluster uses the default oplog size calculated by Atlas. You can check the oplog size by connecting to your cluster via the `mongo` shell and authenticating as a user with the `Atlas admin` role. Run the `rs.printReplicationInfo()` method to view the current oplog size and time. This option corresponds to the `replication.oplogSizeMB` `mongod` configuration file option.

Example¶

Request¶

copy

curl --user "username:apiKey" --include --digest \
 --header "Content-Type: application/json" \
 --request GET "https://cloud.mongodb.com/api/atlas/v1.0/groups/5356823b3794de37132bb7b/clusters/LogData/processArgs"

Response¶

copy

{
  "failIndexKeyTooLong": true,
  "javascriptEnabled": true,
  "minimumEnabledTlsProtocol": "TLS1_1",
  "noTableScan": false,
  "oplogSizeMB": 1000
}

← Get a Single Cluster Create a Cluster →