Closed keliss closed 3 years ago
Also, enabling debug level for logs doesn't change anything.
Damn, compression doesn't work. Setting compress-data = false
solved the issue. I bet this is a bug.
Maybe it just was solved in https://github.com/ClickHouse/ClickHouse/pull/28150
Nevertheless, regarding the point about documentation. Do you find this, for example, difficult to follow? https://github.com/lomik/graphite-clickhouse/blob/master/doc/config.md
It is the same thing I'd like to implement in cch. Unfortunately, I don't have anymore so much time for it since in my current position I don't use the go graphite stack.
As well, worth mentioning, here you can quickly get support https://t.me/ru_go_graphite
Thanks for the links, this is useful.
Regarding the documentation:
cache-ttl = "12h0m0s"
) is used for and what problems it can create like getting stale data or not getting fresh data. Right now I can only hope that everything will work fine with that cache.hash = ""
).context = []
parameter?zero-timestamp=true
is a bad thing, you have to search through PRs to find the answer.huh, well.. ok =) Most of your questions I added to #91
graphite
or prometheus
is defined there, then the table is used only for according requests.Cool, thanks. Sad to hear the project slowly becomes abandoned.
Hi. I'm not able to feed any data into CH because it keeps throwing errors like this when carbon-clickhouse inserts data:
What am I doing wrong? There's nothing in the logs, I can't even see what data is actually being fed into CH. I tried capturing requests to CH, and looks like there's even no data being sent:
Here's my config (by the way, it would be great to actualize all the config params, table SQL queries and provide a more user-friendly description for each param for both carbon-clickhouse and graphite-clickhouse because they are really hard to configure optimally as of now, you have to understand the internals very well):
Thanks.