AIStor supports publishing bucket notification events to a Redis service endpoint. Prerequisites The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a Redis endpoint to an AIStor Server The following procedure adds a new Redis service endpoint for supporting bucket notifications in an AIStor Server.

This section provides documentation for operating and maintaining AIStor Object Store deployments. Use this documentation for Day 2 and ongoing operational tasks in production environments, including monitoring, scaling, troubleshooting, and managing production AIStor deployments. You can find detailed explanations for core concepts that underpin AIStor. Understanding topics like erasure coding, distributed architecture, and data protection mechanisms provide a foundation for effectively using your cluster. AIStor provides comprehensive monitoring capabilities to maintain reliability and performance. Use metrics, logging, audit trails, and healthcheck endpoints to track deployment health and identify performance bottlenecks.

Metrics and alerts AIStor Server publishes point-in-time metrics using the Prometheus Data Model. You can use any scraping tool which supports that data model to pull those metrics into a database for populating historical views, performing query/analysis of metrics data, or creating alerts on preferred data points.

Display npm root

Bump a package version

AIStor supports running in S3 Express Mode. This mode enables directory bucket behavior for optimized heirarchial storage structures. While object store prefixes generally support organized storage, S3 Express Mode implements the specific directory bucket behaviors documented by AWS. S3Express mode disables most API operations outside of simple bucket and object PUT, GET, DELETE, and LIST operations. All other API operations return not supported errors, including operations for versioning, locking, and replication.

NEWS-3.0.0: NEWS for Ruby 3. This document is a list of user visible feature changes since the **2.

format_specifications: Argument +format_string+, which has zero or more embedded _format_ _specifications_ (see below). tt>, which are zero or more objects to be formatted

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.

NEWS: NEWS for Ruby 4. This document is a list of user-visible feature changes since the **3.