-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Summary quantiles respond +Inf if rps decreases to zero #303
Comments
Now it's a part of the quantile algorithm and covers with tests: metrics/test/quantile_test.lua Line 144 in 7652824
We could convert values from empty quantile collector to |
I think it is a good idea |
Line 158 in 7652824
if s.n == 0 then
return nil
end Since |
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
Add separate quantile (`latency_quantile_recent`) and average ( `latency_average`) fields to `crud.stats()` output. `latency` field and tarantool/metrics output remains unchanged. Before this patch, `latency` displayed `latency_quantile_recent` or `latency_average` and there wasn't any was to see pre-computed average if quantiles are enabled. But it may be useful if quantile is `nan`. Quantiles may display `-nan` if there were no observations for a several ages. Such behavior is expected [1] and valid: for example, Grafana should ignore such values and they will be displayed as `No data` for a window when there wasn't any requests. 1. tarantool/metrics#303 Closes #286
If there are 0 new requests for some time, summary collector quantiles respond with +Inf values.
It breaks visualization with ugly vertical lines. I'm sure there are better approaches to handle this.
Reproducer
You may use https://github.com/tarantool/grafana-dashboard docker cluster and stop load container after several minutes.
docker-compose up # let it generate some metrics docker stop grafana-dashboard_load_generator_1
The text was updated successfully, but these errors were encountered: