awesome job by the cortex team!<p>there's a lot of good questions, and some confusion in this thread. here is my view. note: i'm definitely biased; am the co-founder/ceo at grafana labs.<p>- at grafana labs we are huge fans of prometheus. it has become the most popular metrics backend for grafana. we view cortex and prometheus as complementary. we are also very active contributors to the prometheus project itself. in fact, cortex vendors in prometheus.<p>- you can think of cortex as a scale-out, multi-tenant, highly available "implementation" of prometheus itself.<p>- the reason grafana labs put so much resources into cortex is because it powers our grafana cloud product (which offers a prometheus backend). like grafana itself, we are also actively working on an enterprise edition of cortex that is designed to meet the security and feature requirements of the largest companies in the world.<p>- yes, cortex was born at weaveworks in 2016. tom wilkie (vp of product at grafana labs) co-created it while he worked there. after tom joined grafana labs in 2018, we decided to pour a lot more resources into the project, and managed to convince weave.works to move it to the cncf. this was a great move for the project and the community, and cortex has come a long long way in the last 2 years.<p>once again, a big hat tip to everyone who made this release possible. a big day for the project, and for prometheus users in general!<p>[edit: typos]
also props to <a href="https://weave.works" rel="nofollow">https://weave.works</a> for creating cortex, open-sourcing it and moving it under cncf, something this blog post leaves out.
Isn't prometheus an implementation and not an interface? I have "prometheus" running in my cluster, if it's not cortex, what implementation am I using?
Congrats to Grafana Team!<p>If you're looking at scaling your Prometheus setup - check out also Victoria Metrics.<p>Operational simplicity and scalability/robustness are what drive me to it.<p>I used to to send metrics from multiple Kubernetes clusters with Prometheus - each cluster having Prom with remote_write directive to send metrics to central VictoriaMetrics service.<p>That way my "edge" prometheus installations are practically "stateless", easily set up using prometheus-operator. You don't even need to add persistent storage to them.
New to Cortex but when looking at a comparison of Prometheus and InfluxDB (like <a href="https://prometheus.io/docs/introduction/comparison/#prometheus-vs-influxdb" rel="nofollow">https://prometheus.io/docs/introduction/comparison/#promethe...</a>) it appears that Cortex offers similar horizontal scalability features to the InfluxDB Enterprise offering. The linked comparison does note the difference between event logging and metrics recording but I am curious (choosy beggar that I am) whether others consider them separate tooling or whether it is possible to remain performant using one solution.