Fixed metric latency unit and logging (#49)

* move latency_unit into cachet dictionary

* log actual metric latency_unit

* also update config in readme

* also update config description in readme
This commit is contained in:
Patrick Fruh
2019-02-25 06:59:02 +01:00
committed by mtakaki
parent 393aaa0b30
commit f1e69bf39b
3 changed files with 4 additions and 4 deletions

View File

@@ -37,8 +37,8 @@ cachet:
- CREATE_INCIDENT
- UPDATE_STATUS
public_incidents: true
latency_unit: ms
frequency: 30
latency_unit: ms
```
- **endpoint**, the configuration about the URL that will be monitored.
@@ -59,8 +59,8 @@ latency_unit: ms
- **CREATE_INCIDENT**, we will create an incident when the expectation fails.
- **UPDATE_STATUS**, updates the component status
- **public_incidents**, boolean to decide if created incidents should be visible to everyone or only to logged in users. Important only if `CREATE_INCIDENT` or `UPDATE_STATUS` are set.
- **latency_unit**, the latency unit used when reporting the metrics. It will automatically convert to the specified unit. It's not mandatory and it will default to **seconds**. Available units: `ms`, `s`, `m`, `h`.
- **frequency**, how often we'll send a request to the given URL. The unit is in seconds.
- **latency_unit**, the latency unit used when reporting the metrics. It will automatically convert to the specified unit. It's not mandatory and it will default to **seconds**. Available units: `ms`, `s`, `m`, `h`.
## Setting up