From 26574eb04def0b8df8c08cd5ab998828aa845a9c Mon Sep 17 00:00:00 2001 From: Nguyen Hai Truong Date: Tue, 11 Feb 2020 01:32:58 +0700 Subject: [PATCH] docs: Fix typo in docs/storage.md (#6799) `availiablity` -> `availability` Signed-off-by: Nguyen Hai Truong --- docs/storage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/storage.md b/docs/storage.md index 5d8e4a94d..495f6ee5e 100644 --- a/docs/storage.md +++ b/docs/storage.md @@ -43,7 +43,7 @@ The directory structure of a Prometheus server's data directory will look someth ``` -Note that a limitation of the local storage is that it is not clustered or replicated. Thus, it is not arbitrarily scalable or durable in the face of disk or node outages and should be treated as you would any other kind of single node database. Using RAID for disk availiablity, [snapshots](https://prometheus.io/docs/prometheus/latest/querying/api/#snapshot) for backups, capacity planning, etc, is recommended for improved durability. With proper storage durability and planning storing years of data in the local storage is possible. +Note that a limitation of the local storage is that it is not clustered or replicated. Thus, it is not arbitrarily scalable or durable in the face of disk or node outages and should be treated as you would any other kind of single node database. Using RAID for disk availability, [snapshots](https://prometheus.io/docs/prometheus/latest/querying/api/#snapshot) for backups, capacity planning, etc, is recommended for improved durability. With proper storage durability and planning storing years of data in the local storage is possible. Alternatively, external storage may be used via the [remote read/write APIs](https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage). Careful evaluation is required for these systems as they vary greatly in durability, performance, and efficiency.