The horizontally scalable, highly available, multi-tenant, long term storage solution for Prometheus and OpenTelemetry Metrics.| Cortex
Context You can have more than a single Prometheus monitoring and ingesting the same metrics for redundancy. Cortex already does replication for redundancy, and it doesn’t make sense to ingest the same data twice. So in Cortex, we made sure we can dedupe the data we receive from HA Pairs of Prometheus. We do this via the following: Assume that there are two teams, each running their own Prometheus, monitoring different services. Let’s call the Prometheus T1 and T2. Now, if the teams are r...| Cortex – Guides
Tenant ID naming The tenant ID (also called “user ID” or “org ID”) is the unique identifier of a tenant within a Cortex cluster. The tenant ID is opaque information to Cortex, which doesn’t make any assumptions on its format/content, but its naming has two limitations: Supported characters Length Supported characters The following character sets are generally safe for use in the tenant ID: Alphanumeric characters 0-9 a-z A-Z Special characters Exclamation point (!) Hyphen (-) Unders...| Cortex – Guides
Cortex consists of multiple horizontally scalable microservices. Each microservice uses the most appropriate technique for horizontal scaling; most are stateless and can handle requests for any users while some (namely the ingesters) are semi-stateful and depend on consistent hashing. This document provides a basic overview of Cortex’s architecture. The following diagram does not include all the Cortex services, but does represent a typical deployment topology. The role of Prometheus Promet...| Cortex