Managing a Deployment

You can use the AIStor Console to perform many of the deployment monitoring and management functions available in AIStor, such as:

• License to monitor the status and expiration of the MinIO Commercial License used for the AIStor deployment.
• Monitor the health and activity of the deployment by reviewing metrics, server or audit logs, trace history, S3 events, or drive health.
• Configure alerts by adding or managing a notification target.
• Set up site replication to synchronize datacenters for timely access across geographically dispersed workforces or for disaster preparedness.
• Configure deployment settings.

The Overview page displays summary information for a deployment including:

• Capacity and usage
• Drive, server, and pools count and status
• Bucket and object count and size
• User access summary
• Configured event destination targets

Access to any of these sections may be restricted by policy.

The License page shows the current license status of the deployment. The page shows the validity of the license, the date the license was issued, and the date and time the license expires.

Access the license page by selecting the user icon dropdown, then License.

The Debug section provides an interface for monitoring the health and status of the AIStor deployment.

Access the Debug section by selecting the bug icon.

Initiate a health diagnostic report for sending to SUBNET. The resulting health report is intended for use by MinIO Engineering through MinIO SUBNET and may contain internal or private data points, such as hostnames.

This is similar to running mc support diag.

The report includes information such as:

• System settings, services, and configurations that might impact performance
• TLS certificate status, validity, expiration, and algorithm type information
• CPU core count and information
• Drive count, status, size, and available space
• Information about data-containing partitions
• Cluster size server count
• File system type
• Memory size and type
• OS symmetry and Linux kernel version
• Internode latency
• Tiering configurations
• NTP synchronization
• Available resources
• Replication configuration
• AIStor Server version

If desired, you can download the latest report from the page in markdown format.

Monitor API calls as they occur on the system.

This is the same as running mc admin trace.

The Performance section provides an interface for running a performance test of the deployment. The resulting test can provide a general guideline of deployment performance under S3 GET and PUT requests.

For more complete performance testing, consider using a combination of load-testing using your staging application environments and the MinIO WARP tool.

MinIO strongly advises against running the performance tests on a production deployment, as all traffic on the deployment is temporarily suspended during the test.

This is the same as running mc support perf.

The Profile section provides an interface for running system profiling of the deployment. The results can provide insight into the AIStor process running on a given node.

The resulting report is intended for use by MinIO Engineering via MinIO SUBNET. Independent or third-party use of these profiles for diagnostics and remediation is done at your own risk.

This is the same as running mc support profile.

The Inspect section provides an interface for capturing the erasure-coded metadata associated to an object or objects. MinIO Engineering may request this output as part of diagnostics in MinIO SUBNET.

The resulting object may be read using MinIO’s debugging tool. Independent or third-party use of the output for diagnostics or remediation is done at your own risk. You can optionally encrypt the object such that it can only be read if the generated encryption key is included as part of the debugging toolchain.

This is the same as running mc support inspect.

Enable or disable the automatic sending of health diagnostic reports to SUBNET. When enabled, the report automatically runs and uploads to SUBNET every 24 hours.

This is the same as using the mc support callhome command.

The Events section provides an interface to view, add, modify, or remove Event Notification targets.

You can use this screen configure AIStor to push notification events to the one or more target destinations, including Redis, MySQL, Kafka, PostgreSQL, AMQP, MQTT, Elastic Search, NATS, NSQ, or a Webhook.

The Replication section provides an interface for adding and managing the site replication configuration for the deployment.

Configuring site replication requires that only a single site have existing buckets or objects (if any).

The Encryption setting provides an interface for listing, creating, and deleting keys for use with Server-Side Encryption. You must first set up a KMS, such as the AIStor Key Manager, before accessing this page.

You can use keys created or listed in this view for object encryption operations, including setting a bucket-level default key.

The Settings section provides an interface for viewing and retrieving configuration settings for all MinIO Servers in the deployment. Use the buttons to Export and Import the settings between deployments.

This section contains the following subsections.

• Site
• Compression
• API
• Scanner
• Logger Webhook
• Audit Webhook
• Audit Kafka

Environment variable configuration settings override any customizations added in the AIStor Console.

Some subsections may not be visible if the authenticated user does not have the required administrative permissions.

The interface functionality mimics that of using mc admin config get or mc admin config set. Refer to those commands for details on how to define the many options.

Some configuration settings may require restarting the AIStor deployment to apply changes.