mc qos status

The mc qos status command displays QoS metrics and status for a specified bucket.

Added in RELEASE.2025-12-20T04-58-37Z

mc qos status requires AIStor Client RELEASE.2025-12-19T20-11-44Z or later and AIStor Server RELEASE.2025-12-20T04-58-37Z or later.

The command displays a table that provides the following QoS metrics:

API rule applied
Object prefix
Priority level
Configured rate limits
Rule ID
Per-node statistics:
- API name
- Node name
- Throttled requests
- Requests that exceeded the rate limit
- Request timeouts
- Client disconnections

Syntax

Example Syntax

The command has the following syntax:

mc [GLOBALFLAGS] qos status        \
                     TARGET        \
                     [--node]      \
                     [--period]    \

Brackets [] indicate optional parameters.
Parameters sharing a line are mutually dependent.
Parameters separated using the pipe | operator are mutually exclusive.

Copy the example to a text editor and modify as-needed before running the command in the terminal/shell.

Parameters

TARGET

Required

The alias and bucket to check metrics for.

mc qos status myaistor/mybucket

--node

Optional

Specify a specific node in the deployment to retrieve statistics for.

For example:

mc qos status myaistor/mybucket --node minio:9001

--period

Optional

Report metrics for the specified time period.

Valid values:

1m - Last 1 minute (default)
1h - Last 1 hour
all - Since cluster start

For example:

mc qos status myaistor/mybucket --period 1h

Global flags

This command supports any of the global flags.

Example

Display QoS metrics for the last hour from a specific node

The following command displays QoS metrics for the mybucket bucket on the myaistor deployment for the last one hour from a specific node:

mc qos status myaistor/mybucket --period 1h --node minio:9001

S3 compatibility

The mc commandline tool is built for compatibility with the AWS S3 API and is tested with AIStor and AWS S3 for expected functionality and behavior.

MinIO provides no guarantees for other S3-compatible services, as their S3 API implementation is unknown and therefore unsupported.

While mc commands may work as documented, any such usage is at your own risk.

Permissions

You must have appropriate permissions on the deployment to view QoS status.