Mikhail f. Shiryaev

From my personal experience, `auto` is useful only when you migrate the backend from one to another protocol. But even then, it's useless, because you have to restart carbonapi, since...

My five cents: we use grafana annotations in the company

> And same goes for carbon-clickhouse (that is there ensured on carbon-clickhouse and graphite-clickhouse layers as far as I remember) Just as a tiny detail, cch sends the points as...

Kinda =) In the end, it gets aligned points directly from CH, which matches the original whisper approach. I'd say, CH aligns them. Sorry for offtopic though

> What X-Gch-Request-Id will be passed for /render queries (2 requests - find and data with different request ids) ? I'd suggest to use comma separated values. Like X-Forwarded-For

Actually, separated find shouldn't be a case. Carbonapi must omit it and send pain render request with glob. But it will send different render requests per target, so the case...

Could you check, please, if #529 fixes it? **update** Actually, after careful reading, I've recognized that I don't see an issue here. If you'd take a look, here is a...

Hey @sylvain-beugin, any following up here?

The best thing I can see here is putting all ports down and writing an ERROR to log. Does it sound like a good solution?

Hey, the readme is correct, index table should be used https://github.com/lomik/graphite-clickhouse/wiki/IndexTable It makes sense for sure to change the defaults