mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-18 14:40:26 +01:00
79008b712f
VM has different responses to equivalent queries for MetricsQL and GraphiteQL in case of failed access to one of vmstorage node of the cluster vmstorage nodes. For GraphiteQL, the denyPartialResponse feature is not used, it is always true, which is not always correct (depending on the configuration). In the PR I have removed the hardcoded denyPartialResponse for GraphiteQL, just like MetricsQL does. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). |
||
---|---|---|
.. | ||
clusternative | ||
deployment | ||
graphite | ||
graphiteql | ||
multiarch | ||
netstorage | ||
prometheus | ||
promql | ||
querystats | ||
searchutils | ||
static/css | ||
vmui | ||
main.go | ||
Makefile | ||
README.md | ||
vmui.go |
vmselect
performs the following tasks:
-
Splits incoming selects to tasks for
vmstorage
nodes and issues these tasks to all thevmstorage
nodes in the cluster. -
Merges responses from all the
vmstorage
nodes and returns a single response.
The vmui
directory contains static contents built from app/vmui package with make vmui-update
command. The vmui
page is available at http://<vmselect>:8481/select/<accountID>/vmui/
.