-
At the moment, each metric for a given target is fetched in parallel, but the targets themselves are processed serially. For queries with a large number of targets, this can can unnecessary slow down…
-
Hi,
I noticed that root metric names starting with digit and followed by a dash are not accepted while they are in the legacy graphite-web.
587-AL --> K.O.
AAA-587 --> OK
587AAA ---> OK
AAA5…
-
We have mongo metrics, they are displayed normally in graphite-web. We don't use Tags. but in carbonapi we get error
```
Bad Request: Bad Request Target : collectd.TEST.rtmtestnbohl03.27011[cluste…
-
Apart from being delicious, delicious betrayal, having Prometheus monitor go-carbon is useful when running the system at scale to avoid a "who watches the watchmen" situation.
I have some work towa…
-
**Describe the bug**
When the service is killed by the OS due to OOM, the systemd automatically starts it again.
Then, the memory consumption in the machine steadily increases for 8-9 days until ne…
-
Following pic showing that each physical node is receiving approx 1.4M of metrics but three PODs are running on each physical node .. PODs are not sharing equal load. ex: go-graphite-node-2 POD ending…
-
how to configure carbon-clikhouse with clickhouse distributed tables ?
-
# Problem
Some functions in graphite-web re-fetch data while evaluating. Current architecture of carbonapi doesn't allow such operation and the results are not equal.
Function like **hitcount** in g…
-
**Is your feature request related to a problem? Please describe.**
Some Graphite web functions, such as the holtWinters functions, group, example, etc. are missing tests.
**Describe the solution …
-
**Problem Description**
We are running **go-carbon 0.15.6** as a backend for **go-carbonapi 0.14.0** and as the number of metrics has kept increasing (~1.6TB of *.wsp files), performance kept degra…