AIStor Server supports publishing bucket notification events to an Elasticsearch service endpoint. Prerequisites Elasticsearch v7.0 or later. MinIO AIStor relies on the v7 project for Elastic connectivity. The elastic/v7 library specifically targets Elasticsearch v7.0 and is not compatible with earlier Elasticsearch versions.

Healing is MinIO 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 MinIO AIStor can restore a damaged object depending on the following variables;

This guide covers tools and techniques for debugging MinIO AIStor deployments. HTTP tracing Use mc admin trace to capture real-time HTTP API calls to and from the MinIO AIStor server. Default trace shows only API operation names and HTTP response status:

This page documents the RESTful API endpoints for managing bucket inventory configurations. All inventory operations are scoped to a bucket and use the ?minio-inventory query parameter. For CLI-based management, see mc inventory. For configuration details, see the Configuration Reference. Permissions Inventory API endpoints require the following IAM permissions:

This page provides a complete reference of all v3 metrics available in MinIO AIStor. All metrics are available under the base endpoint /minio/metrics/v3. See Metrics and Alerts for configuration and Prometheus integration. Table of Contents API (29 metrics) API Requests (18 metrics) Bucket API (11 metrics) Audit (11 metrics) Batch (5 metrics) Batch Jobs (3 metrics) Bucket Batch (2 metrics) Cluster (47 metrics) Cluster Config (5 metrics) Cluster Erasure Set (11 metrics) Cluster Health (9 metrics) Cluster Usage Buckets (11 metrics) Cluster Usage Objects (11 metrics) Debug (5 metrics) Debug Erasure Sets (1 metrics) Debug Heal (4 metrics) ILM (20 metrics) IAM (11 metrics) Logger Webhook (4 metrics) Notification (8 metrics) Replication (75 metrics) Bucket Replication (22 metrics) Cluster Replication (32 metrics) Node Replication (21 metrics) Scanner (6 metrics) System (140 metrics) System CPU (34 metrics) System Drive (31 metrics) System Drive SMART (11 metrics) System Memory (24 metrics) System Network Certificate (1 metrics) System Network Interface (12 metrics) System Network Internode (9 metrics) System Process (18 metrics) Heal (5 metrics) KMS (6 metrics) Lambda (3 metrics) Locks (8 metrics) Software (2 metrics) Stdout (5 metrics) Tier (3 metrics) Delta Sharing (14 metrics) Tables (14 metrics) API Path Description /api/requests Metrics about API requests served by the current node. /bucket/api Per-bucket API request metrics. Requires bucket query parameter. API Requests Path: /api/requests

AIStor exposes metrics, audit-log entries, and alerting hooks for the AIStor Tables (Apache Iceberg REST Catalog) and AIStor Table Sharing (Delta Sharing) APIs. Use these signals to monitor request volume, latency, authentication, caching, and rate limiting for table and share workloads. This page describes the available metrics, how table and share operations appear in audit logs, and example Prometheus alerting rules. Metrics Tables and Delta Sharing publish metrics on both the v3 and v2 metrics endpoints.

MinIO AIStor supports OpenTelemetry-based distributed tracing to capture and analyze request flows across the server. Traces can be streamed to an OTLP-compatible collector, recorded to a local file, or captured on-demand for troubleshooting. Architecture MinIO AIStor exports trace data using the OpenTelemetry Protocol (OTLP) over HTTP:

This guide covers common TLS certificate errors in MinIO AIStor deployments and provides procedures for diagnosing and resolving them. For general TLS setup, see the platform-specific network encryption guides under Installation. For cert-manager integration, see TLS certificate management with cert-manager. Common error messages Certificate signed by unknown authority x509: certificate signed by unknown authority The server presented a certificate signed by a CA that the client does not trust.

Metrics version 2 provides metrics organized into four categories: Cluster metrics Bucket metrics Resource metrics Node 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.

MinIO AIStor provides S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) disk health monitoring for proactive detection of drive failures. SMART monitoring collects health telemetry directly from NVMe and SATA drives using native Linux ioctl calls with no external dependencies. Enabling SMART metrics Prometheus metrics (v3) SMART metrics are available at the /system/drive/smart collector path. See Metrics v3 Reference for the full metric listing.