Last time we tested Cortex we encountered two minor issues: floating-point input timestamps were not rounded in the same way as in Prometheus, and the system did not support executing queries without a metric name.
This is currently not configurable on the Grafana Cloud side, so we had to apply a cross-cutting query tweak to align input timestamps to our reference Prometheus server in the same way, to get comparable results.
With this in mind, we tested a Grafana Cloud account via remote_write and their Prometheus-style HTTP query API on both the remaining legacy cluster and a new dedicated blocks-storage cluster, and we got the same 99.62% and 100% test scores as for Cortex itself.
MetricFire is still using a slightly outdated version of Cortex, so we ran into similar input timestamp parsing inaccuracies as with Cortex in August, and queries without a metric name are not yet supported due to using chunks-based storage.
That's the vision — and if that resonates with you, say hello!We have several positions open:* Senior Site Reliability Engineer (SF, Seattle, US Remote or Portugal)* Senior Software Engineer, Frontend (Portugal) * Software Engineer, Frontend (Portugal)* Software Engineer, Database Engine (SF, Seattle, US Remote or Portugal)Careers page with individual links for each open position: https://www.singlestore.com/careers/jobs/If you want to learn more about the engineering work we do, check out singlestore.engineering.Feel free to email directly at david at memsql dot com.