The mc support perf client command measures the network throughput from the local device running the AIStor Client to the server. Use this command to identify potential network performance bottlenecks between the client and server. Syntax Example The following command tests the network throughput from the local device to the server with alias myaistor for 30 seconds.

The mc support telemetry replay command replays a file of telemetry data to an OpenTelemetry collector. You can record a file to replay later with mc support telemetry record. Syntax Example The following command replays a local file of telemetry data to a localhost OTLP server.

The mc support diag command generates a health report for an AIStor deployment. The command generates and uploads the health report to SUBNET for analysis. Automated with Call Home The report is automatically generated and uploaded every 24 hours with Call Home, which can be disabled or enabled at any time. The resulting health report is intended for use by MinIO Engineering through SUBNET and may contain internal or private data points. Exercise caution before sending a health report to a third party or posting the health report in a public forum.

This page covers settings that manage access and behavior for the AIStor Console. 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 manage access and behavior for the batch job 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.

This page documents settings for configuring an MQTT service as a target for Bucket Notifications. See Publish Events to MQTT 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 section documents settings that control behavior related to AIStor metrics and logging. See Metrics and Alerts for more information. 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.

The following section documents environment variables for configuring AIStor to publish audit logs to an HTTP webhook endpoint. See Publish Audit Logs to HTTP Webhook for more complete documentation and tutorials on using these environment variables. Example Environment Variables You can specify multiple webhook endpoints as audit log targets by appending a unique identifier _ID for each set of related logging settings.

AIStor Server uses the built-in scanner to check objects for healing and to take any scheduled object actions. Such actions may include: calculate data usage on drives evaluate and apply configured lifecycle management or object retention rules perform bucket or site replication check objects for missing or corrupted data or parity shards and perform healing The scanner performs these functions at two levels: cluster and bucket. At the cluster level, the scanner splits all buckets into groups and scans one group of buckets at a time. The scanner starts with any new buckets added since the last scan, then randomizes the scanning of other buckets. The scanner completes checks on all bucket groups before starting over with a new set of scans.

The mc replicate ls command lists all replication rules on an AIStor bucket. The output includes the remote bucket, rule ID, priority, and ARN for each rule. Syntax Example The following command lists all enabled replication rules for the mydata bucket on the myaistor AIStor deployment: