-
In the latest clickhouse version, clickhouse is exporting metrics about devices, and this is generating metric names with hyphens in them, which are not valid for prometheus and scraping fails
```
…
-
Keeping the POD annotations is essential to run the workload in EKS, where the fargate profile is the default one.
Dropping essential annotations, such as `"eks.amazonaws.com/compute-type" = "ec2"`…
-
**Use case**
Efficiently querying continuous profiling data in ClickHouse to drive flamegraph visualization would be a great addition to the [logging, metrics and traces use case](https://clickhous…
yawnt updated
3 weeks ago
-
After https://github.com/ClickHouse/ClickHouse/pull/57236 and https://github.com/ClickHouse/ClickHouse/pull/56771 we can create new specialized dashboards. But those features have not been used for no…
serxa updated
1 month ago
-
Here's the end-user flow we'd like:
- Through the console (or perhaps the CLI?) a user can view *metrics* for some category of information. For example: "show me the metrics for HTTP endpoint laten…
-
I have a replicated cluster (3 nodes: 54 cpu, 256gb each). All nodes are replica. Inserts mostly goes on one node. Selects on another two.
Every night in ~00-00 something generate huge load (LA) on *…
-
In the UI, while creating Dashboards it'd be nice if there's toggle to search based on only prefix matching.
eg in the below screenshot, I'm only interested in looking into Kafka_* metrics not clickh…
-
opentelemetry-101_collector_1 exited with code 1
Logs :
`collector_1 | Error: failed to get config: cannot unmarshal the configuration: 1 error(s) decoding:
collector_1 |
collector_1 | *…
-
### Describe the bug
When executing a prepared query statement, the SQL client returns `only Exec method supported in batch mode`.
### Steps to reproduce
1. `docker run --name clickhouse -p 900…
-
It would be really useful to support autoscaling clickhouse cluster based on some events or metrics similar to how KEDA does.