Menu
Open source
Pyroscope query-frontend
The query-frontend is a stateless component that provides the same API as the querier and can be used to accelerate the read path and ensure fair scheduling between tenants using the query-scheduler.
In this situation, queriers act as workers that pull jobs from the queue, execute them, and return the results to the query-frontend for aggregation.
We recommend that you run at least two query-frontend replicas for high-availability reasons.
Because the query-scheduler is a mandatory component when using the query-frontend, you must run at least one query-scheduler replica.
The following steps describe how a query moves through the query-frontend.
- A query-frontend receives a query.
- The query-frontend places the query in a queue by communicating with the query-scheduler, where it waits to be picked up by a querier.
- A querier picks up the query from the queue and executes it.
- A querier or queriers return the result to query-frontend, which then aggregates and forwards the results to the client.
Was this page helpful?
Related resources from Grafana Labs
Additional helpful documentation, links, and articles:
Video
Getting started with continuous profiling with Grafana Cloud Profiles
In this webinar, you'll learn how to get started with Grafana Cloud Profiles - a hosted continuous profiling tool in Grafana Cloud
Continuous profiling with Grafana Pyroscope: developer experience, flame graphs, and more
Learn about the new Grafana Pyroscope open source project and how continuous profiling can improve developer experience.
Building scalable OSS observability with Mimir, Loki, Tempo, and Pyroscope
Learn the latest scalability and performance improvements in OSS telemetry backends Loki, Tempo, Mimir, and Pyroscope for profiles. Watch on demand.