Plan your storage for the OpenShift Logging Loki stack
=====================================================

Scope
-----
Red Hat OpenShift Container Platform customers

Severity
--------
Important

Description
-----------

In OpenShift Logging 5.8, the Elasticsearch based stack was marked as deprecated. Deprecated does not removed, but customers are invited to consider the alternative Loki stack for logging, and report to Red Hat if they have a use case which is not covered by the Loki stack.

One important factor to consider is that the Loki stack requires Object Storage to store the logs chunks. Supported Object Storages include AWS S3, Google Cloud Storage, Azure, Swift, Minio or the Red Hat OpenShift Data Foundation S3 storage.

Object Storage is well suited for static data that you don't need to modify, and its agility and flat nature means it can scale to extremely large quantities of data. Also in public cloud environments Object Storage is cost efficient: you only pay for what you use.
These properties of Object Storage are a good fit for storing log data, which is why the upstream Loki project recommends its usage and OpenShift Logging with the Loki stack require it.

Resources
---------

[File storage, block storage, or object storage ?](https://www.redhat.com/en/topics/data-storage/file-block-object-storage)

[General Availability of OpenShift Logging with the Loki stack](https://docs.openshift.com/container-platform/4.10/logging/v5_5/logging-5-5-release-notes.html#logging-5-5-0-enhancements)

[ElasticSearch, Fluentd, Kibana deprecation notice](https://docs.openshift.com/container-platform/4.14/logging/logging_release_notes/logging-5-8-release-notes.html)

[Migrating the default log store from Elasticsearch to Loki in OCP 4 ](https://access.redhat.com/articles/6991632)

[How to migrate Fluentd to Vector in Red Hat OpenShift Logging 5.5+ versions ? ](https://access.redhat.com/articles/6999658)