1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-01-20 00:08:02 +01:00

chore(changelog): prepare 3.1.3 release

This commit is contained in:
ivaosthu 2018-11-28 16:28:30 +01:00 committed by Ivar Conradi Østhus
parent 05ec618fea
commit 26380e6e60
2 changed files with 7 additions and 1 deletions

View File

@ -1,5 +1,9 @@
# Changelog # Changelog
## 3.1.3
- fix(metrics): Add prometheus compatible feature metrics endpoint
## 3.1.2 ## 3.1.2
- fix(clientApi): Add namePrefix paramter to /api/client/features - fix(clientApi): Add namePrefix paramter to /api/client/features

View File

@ -15,8 +15,10 @@ Unleash uses prometheus internally to collect metrics. These are available on th
Unleash will automatically count all updates for all toggles under the metric name `feature_toggle_update_total`, and the toggle name is will be set as a label value. This information can be used to create annotations in grafana for everytime a feature toggle is changed. Unleash will automatically count all updates for all toggles under the metric name `feature_toggle_update_total`, and the toggle name is will be set as a label value. This information can be used to create annotations in grafana for everytime a feature toggle is changed.
You can use this query in grafana to achive this: You can use this query in grafana to achieve this:
``` ```
delta(feature_toggle_update_total{toggle="Demo"}[1m]) != bool 0? delta(feature_toggle_update_total{toggle="Demo"}[1m]) != bool 0?
``` ```
Another useful counter is the `feature_toggle_usage_total` which will give you the numbers for how many time a feature toggle has been evaluated to `active` or not.