![]() ![]() ![]() ![]() How often it splits them is determined by the querier.split-queries-by-interval flag or the yaml config query_range.split_queriers_by_interval. One of the most important functions of the query frontend is the ability to split larger queries into smaller ones, execute them in parallel, and stitch the results back together. However, that doesn’t help when our queries are too large for a single querier to execute. Sometimes we can solve this with more queriers. A common bottleneck is on the read path: queries that executed effortlessly on small data sets may churn to a halt on larger ones. As we become more comfortable with its paradigms and begin migrating towards a more production ready deployment there are a number of things to be aware of. It’s a common occurrence to start running Grafana Loki as a single binary while trying it out in order to simplify deployments and defer learning the (initially unnecessary) nitty gritty details. You should override them with specifics to your environment. This aims to be a general purpose example there are a number of substitutions to make for it to work correctly. Query Frontend Kubernetes Query Frontend Example Disclaimer ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |