ClickHouse / ClickHouse/ClickHouse

Protocols -> type: prometheus

Open
#74,416 0 comments 0 reactions 0 assignees View on GitHub
comp-keeper external unexpected behaviour
Dominant language
C++
Stars
49.9k
Forks
9k
Avg merge
21h 32m
Merged PRs (30d)
515

Description

**Describe the unexpected behaviour**
I tried to make the Prometheus exporter to listen to 0.0.0.0:9363. Still, this isn't working, no matter what I try.

**How to reproduce**
* Which ClickHouse server version to use
```
# clickhouse-keeper --version
ClickHouse keeper version 24.12.2.29 (official build).
```

* Which interface to use, if matters: doesn't matter
* Non-default settings, if any
```


trace
/var/log/clickhouse-keeper/clickhouse-keeper.log
/var/log/clickhouse-keeper/clickhouse-keeper.err.log
1000M
10

4096


9181

1

/var/lib/clickhouse/coordination/logs
/var/lib/clickhouse/coordination/snapshots


10000
10000
100000
information
true

true


1
keeper1
9234


2
keeper2
9234


3
keeper3
9234



/metrics
9363
true
true
true
true



prometheus>
0.0.0.0
9362

```

**Expected behavior**
I would expect Prometheus to listen on 0.0.0.0:9363 or 0.0.0.0,9362, but it always listens on 127.0.0.1:9363.

**Tried things**
Relevant config presented only, to avoid making this too long:
```
[...]

/metrics
0.0.0.0
9363
true
true
true
true

```
Another one:
```
[...]

/metrics
0.0.0.0
9363
true
true
true
true

```
Another one:
```

/metrics
true
true
true
true



prometheus>
0.0.0.0
9363

```
The only thing that made it work, but it's not what I want is to specify the `0.0.0.0` under the tag. The only issue with this is that ALL listeners will listen on 0.0.0.0 (normal behavior but I don't want everything on the network).

Thank you!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.