Docs Menu
Docs Home
/ /
Atlas CLI
/ / /

atlas api accessTracking listAccessLogsByHostname

On this page

  • Syntax
  • Options
  • Inherited Options

experimental: Returns the access logs of one cluster identified by the cluster's hostname.

Access logs contain a list of authentication requests made against your clusters. You can't use this feature on tenant-tier clusters (M0, M2, M5). To use this resource, the requesting API Key must have the Project Monitoring Admin role or the Project Database Access Admin role.

This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Access-Tracking/operation/listAccessLogsByHostname.

For more information and examples, see the referenced API documentation linked above.

Command Syntax
atlas api accessTracking listAccessLogsByHostname [options]
Name
Type
Required
Description

--authResult

false

flag that indicates whether the response returns the successful authentication attempts only

--end

int

false

date and time when to stop retrieving database history

--envelope

false

flag that indicates whether Application wraps the response in an envelope JSON object

--groupId

string

true

unique 24-hexadecimal digit string that identifies your project

-h, --help

false

help for listAccessLogsByHostname

--hostname

string

true

fully qualified domain name or IP address of the MongoDB host that stores the log files that you want to download

--ipAddress

string

false

one Internet Protocol address that attempted to authenticate with the database

--nLogs

int

false

maximum number of lines from the log to return

--output

string

false

preferred api format, can be ["json", go-template] This value defaults to "json".

--output-file

string

false

file to write the api output to. This flag is required when the output of an endpoint is binary (ex: gzip) and the command is not piped (ex: atlas command > out.zip)

--pretty

false

flag that indicates whether the response body should be in the prettyprint format

--start

int

false

date and time when MongoDB Cloud begins retrieving database history

--version

string

false

api version to use when calling the api call [options: "2023-01-01"], defaults to the latest version or the profiles api_version config value if set This value defaults to "2023-01-01".

Name
Type
Required
Description

-P, --profile

string

false

Back

listAccessLogsByClusterName