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.

You can use the AIStor Console to perform several of the bucket and object management and interaction functions available in AIStor. Depending on the permissions and IAM policies for the authenticated user, you can: Browse, upload, revert, manage, and interact with objects. Browse, create, and manage buckets. Create or monitor remote tiers for object transition rules. Object Browser The Object Browser lists the buckets and objects the authenticated user has access to on the deployment.

The mc admin accesskey ls command lists users, access keys, or temporary security token service keys managed by the AIStor deployment. You can use mc admin accesskey ls as an alias to this command. Syntax Example The following command lists all access keys associated to the user with username admin1 on the deployment at alias myaistor:

The mc admin accesskey rm command removes an access key associated to a user on the deployment. The command requires the access key to exist. Syntax Example The following command removes the access key myuseraccesskey from the myaistor deployment:

Healing is AIStor’s ability to restore an object that has been damaged, corrupted, or partially lost. The loss can come from multiple types of corruptions or loss, such as but not limited to: drive-level errors or failure OS or filesystem errors or failure bit rot Healing and erasure coding AIStor can restore a damaged object depending on the following variables;

AIStor Server publishes its server logs to the system console. These logs can include errors, information output, or other information useful during troubleshooting or debugging. Server logs do not emit for all operations and cannot support audit trail or similar compliance requirements. If you require such a trail, configure and use audit logging instead. You can read the server logs using any of the following methods: Run journalctl -u minio from any host machine. Run mc admin logs against the AIStor deployment. Publish server logs to HTTP webhook AIStor supports publishing logs to a webhook consumer through an HTTP PUT operation, where the body of the request is the log as a JSON document.

The mc admin accesskey enable command enables an existing access key. The command requires the access key to exist and be currently disabled. Syntax Example The following command enables the access key myuseraccesskey on the myaistor deployment:

This page documents settings for configuring a MYSQL service as a target for Bucket Notifications. See Publish Events to MySQL for a tutorial on using these settings. 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.

This page covers settings that configure the Erasure Code parity to use for objects written to the AIStor cluster. This impacts how AIStor uses the space on the drive(s) and how AIStor can recover objects stored on lost drives or similar issues. 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.

This page covers deprecated settings that control core behavior of the AIStor Server process. Settings on this page may be removed at any time. Users should migrate to the recommended replacement at the earliest opportunity. 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 Server uses the environment variable value.