Metrics version 2 provides metrics organized into three categories: Cluster metrics Bucket metrics Resource metrics Each v2 endpoint returns all metrics for its category. For example, scraping the following endpoint returns all cluster metrics: http://HOSTNAME:PORT/minio/v2/metrics/cluster The base endpoint alone, /minio/v2/metrics/, returns cluster metrics. For more flexible scraping and a wider range of metrics, use version 3 metrics. Existing deployments can continue to use version 2 metrics.

The AIStor Client (mc) is a drop-in replacement for the Open Source MinIO Client. AIStor mc has exclusive functionality intended to support licensed AIStor Server deployments. mc has the following syntax: mc [GLOBALFLAGS] COMMAND --help See Command Quick Reference for a list of supported commands. Version Alignment with AIStor Server The AIStor Client releases separately from AIStor Server.

Removes one or more IAM policies from either a MinIO-managed user or a group. This command is intended for managing policy associations for MinIO-managed users only. For detaching policies to OpenID-managed users, see OpenID Connect Access Management. For detaching policies to Active Directory/LDAP users or groups, use mc idp ldap policy detach.

Syntax Example The following command lists all anonymous links for the mydata bucket on the myminio AIStor deployment: mc anonymous links myminio/mydata Syntax The command has the following syntax:

The mc tag remove command removes all tags from a bucket or object. Syntax Example The following command removes tags for the mydata bucket on the myminio AIStor deployment:

Description The mc ilm tier command and its subcommands configure a remote supported S3-compatible service for AIStor Lifecycle Management: Object Transition (“Tiering”). After creating one or more tiers with this command, use mc ilm rule and its subcommands to create the rules that move objects to other storage.

The mc ilm rule edit command modifies an existing object lifecycle management rule on an AIStor bucket. Syntax Example The following command modifies existing lifecycle management rules for the mydata bucket on the myminio deployment:

The mc mv command moves an object from source to the target, such as between AIStor deployments or between buckets on the same AIStor deployment. mc mv also supports moving objects between a local filesystem and AIStor. You can also use mc mv against the local filesystem to produce similar results to the mv commandline tool. Syntax Example The following command moves objects from the mydata bucket to the archive bucket on the myminio AIStor deployment:

The mc ilm tier info command outputs statistics about a tier or all tiers for a deployment. Syntax Example The following example outputs the configuration for an existing remote tier called WARM-TIER on the myminio deployment.

This page covers settings that control core behavior of the AIStor process. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.