Alexey Zhiltsov
Alexey Zhiltsov
I am wondering is it hard to implement multiple connections per destination, so it would not try to push everything via one tcp connection. While using hashing can I use...
When relay can't send a metrics out it keeps them in a memory till certain limit. It will be useful to store them on a disk when the memory buffer...
If you using backfill with list of relocated/renamed files in json it keeps original files in place. It useful to have --delete option in order to delete source files once...
If you truncate the kafka topic while carbonsearch trying to do initial warm-up, then carbonsearch gets confused and newer reach the warm state. ``` 2018/02/22 19:19:32 kafka consumer: topic sm_metrics...
It a nice feature to have. Query could be done via HTTP API call. The use-case is to find where does this metric come from. What do you think?
https://github.com/bookingcom/carbonapi/issues/52 the same query find: ```json "level": "ERROR", "timestamp": "2019-02-05T14:27:17.578+0100", "logger": "access", "message": "find failed", "handler": "find", "url": "/metrics/find/?format=protobuf&query=bla", "peer": "1.1.1.1", "carbonapi_uuid": "7652d624-c031-4384-8bc2-c96039beb7be", "query": [ "bla" ], "format": "protobuf", "runtime_seconds":...
We noticed that metrics from some hosts are having gaps. It turned out that go-carbon sometime by some reason delaying metrics with it internal stats by some amount of seconds...
With loose settings of max-globs = 1000 and high rate of requests (find+render) the go-trigram.intersect consumes all CPU cores and prevents metrics from flushing to disk ![profile001](https://user-images.githubusercontent.com/8709761/30425369-41d8ee26-9949-11e7-88d5-19e979557562.png) . perf top...
Same as #206 but with trigram-index = true ``` pi@pi:~/carbon $ /home/pi/carbon/go-carbon -daemon -config /home/pi/carbon/go-carbon.conf [2017-10-13T22:55:36.411+0200] INFO [carbonserver] starting carbonserver {"whisperData": "/mnt/carbon/whisper", "maxGlobs": 100, "scanFrequency": "5m0s"} [2017-10-13T22:55:36.412+0200] INFO [carbonserver] listening...
Currently there is only time and url for 'Slow Request' is does not allow chasing the request up to the carbonapi