Replace unicode chars
This commit is contained in:
12
README.md
12
README.md
@@ -12,9 +12,9 @@ The CSV reports the 24-hour uptime percentage for each CT log URL broken down by
|
||||
|
||||
| Metric | Labels | Description |
|
||||
|---|---|---|
|
||||
| `ct_log_uptime_ratio` | `log_url`, `endpoint` | 24h uptime as a ratio (0–1) |
|
||||
| `ct_log_uptime_fetch_success` | — | 1 if the last fetch succeeded, 0 otherwise |
|
||||
| `ct_log_uptime_fetch_timestamp_seconds` | — | Unix timestamp of the last fetch attempt |
|
||||
| `ct_log_uptime_ratio` | `log_url`, `endpoint` | 24h uptime as a ratio (0-1) |
|
||||
| `ct_log_uptime_fetch_success` | | 1 if the last fetch succeeded, 0 otherwise |
|
||||
| `ct_log_uptime_fetch_timestamp_seconds` | | Unix timestamp of the last fetch attempt |
|
||||
|
||||
Standard `go_*` and `process_*` metrics are also exposed.
|
||||
|
||||
@@ -34,9 +34,9 @@ Metrics are served at `http://localhost:9781/metrics`.
|
||||
| `-listen` | `:9781` | Address to listen on |
|
||||
| `-url` | `https://www.gstatic.com/ct/compliance/endpoint_uptime_24h.csv` | URL of the uptime CSV |
|
||||
| `-interval` | `12h` | How often to fetch the CSV |
|
||||
| `-jitter` | `5m` | Maximum ±jitter applied to the fetch interval |
|
||||
| `-jitter` | `5m` | Maximum +/-jitter applied to the fetch interval |
|
||||
|
||||
The exporter fetches the CSV once on startup, then repeats every `-interval` ± a random value up to `-jitter`. This avoids thundering-herd effects if multiple instances run in parallel.
|
||||
The exporter fetches the CSV once on startup, then repeats every `-interval` +/- a random value up to `-jitter`. This avoids thundering-herd effects if multiple instances run in parallel.
|
||||
|
||||
## Example Prometheus scrape config
|
||||
|
||||
@@ -49,4 +49,4 @@ scrape_configs:
|
||||
|
||||
## License
|
||||
|
||||
Apache 2.0 — see [LICENSE](LICENSE).
|
||||
Apache 2.0 - see [LICENSE](LICENSE).
|
||||
|
||||
Reference in New Issue
Block a user