Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Grafana Phlare deployment modes
In March 2023, Grafana Labs acquired Pyroscope, the company behind the eponymous open source continuous profiling project. As a result, the Pyroscope and Grafana Phlare projects will be merged under the new name Grafana Pyroscope. To learn more, read our recent blog post about the news.
You can deploy Grafana Phlare in one of two modes:
- Monolithic mode
- Microservices mode
The deployment mode is determined by the -target parameter, which you can set via CLI flag or YAML configuration.
Monolithic mode
The monolithic mode runs all required components in a single process and is the default mode of operation, which you can set by specifying -target=all. Monolithic mode is the simplest way to deploy Grafana Phlare and is useful if you want to get started quickly or want to work with Grafana Phlare in a development environment. To see the list of components that run when -target is set to all, run Grafana Phlare with the -modules flag:
./phlare -modules
Microservices mode
In microservices mode, components are deployed in distinct processes. Scaling is per component, which allows for greater flexibility in scaling and more granular failure domains. Microservices mode is the preferred method for a production deployment, but it is also the most complex.
In microservices mode, each Grafana Phlare process is invoked with its -target parameter set to a specific Grafana Phlare component (for example, -target=ingester or -target=distributor). To get a working Grafana Phlare instance, you must deploy every required component. For more information about each of the Grafana Phlare components, refer to Architecture.
If you are interested in deploying Grafana Phlare in microservices mode, we recommend that you use Kubernetes.
