clickhouse-operator: Unexpected metrics-exporter behavior

I have set up the clickhouse operator and wanted to collect metrics from it. I use the prometheus operator as well so I just defined a service monitor to start scraping.

2021-02-19-100032_1088x196_scrot The job is up and running and I can see the scrapes coming in on the metrics-exporter through logs:

I0219 10:03:23.822198       1 exporter.go:98] Finished Collect
I0219 10:03:33.822924       1 exporter.go:88] Starting Collect
I0219 10:03:33.822945       1 exporter.go:98] Finished Collect
I0219 10:03:43.822285       1 exporter.go:88] Starting Collect
I0219 10:03:43.822303       1 exporter.go:98] Finished Collect
I0219 10:03:53.822311       1 exporter.go:88] Starting Collect
I0219 10:03:53.822333       1 exporter.go:98] Finished Collect

Yet when I go to inspect my metrics, I can see a list of all available metrics yet there is only 1 entry for each of these 2021-02-19-102340_1826x541_scrot

This is the case for all metrics… I tried to find similar issues but to no avail. Prometheus isn’t showing any errors whatsoever, weird thing is, I even saw the appended samples/scrape targets go up when I deployed the service monitor object.

Querying yields the same result in the Prometheus built in graph tool. All my other metrics (custom instrumentation, dependencies and kubernetes metrics) are running normally.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 20

Commits related to this issue

Most upvoted comments

ok. echo “mypassword” | sha256sum show exactly same whihc contains in <password_sha256_hex>XXXXX</password_sha256_hex> ?