# Is "value" in metrics (rally-metrics-\* index) aggregated? **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [November 1, 2017, 1:25pm UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034 "2017-11-01T13:25:35Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)\ **Post date:** [November 1, 2017, 1:25pm UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/1 "2017-11-01T13:25:36Z")
Hi, I am wondering if this value an aggregated value in some time interval or if result of all queries are stored? I am using and modifying rally-eventdata-track and in particular combined-indexing-and-querying and want to measure highest latency over time (95+ percentiles). Regards /Johan ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [November 2, 2017, 9:03am UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/2 "2017-11-02T09:03:37Z")
Documents with `service_time` or `latency` in the `name` field are generated per operation. I believe the rest is summary or aggregated results. ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [November 6, 2017, 8:23am UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/3 "2017-11-06T08:23:15Z")
Hi, as @Christian_Dahlqvist has answered, the samples in `rally-metrics-*` are raw samples (one entry per request/response). Throughput samples are aggregated once per second. If you are after specific percentiles, Rally stores the summary report per benchmark in `rally-results-*` (the one that you see on the command line at then end of a race). I.e. you may have thousands of (raw) metrics documents in `rally-metrics-*` but only one summary document in `rally-results-*`. If you want to calculate specific percentiles that are not pre-calculated by Rally (e.g. 95th percentile) I suggest that you use the raw metrics to do that. ---
**Author:** ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)\ **Post date:** [November 6, 2017, 9:02am UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/4 "2017-11-06T09:02:55Z")
Thanks both of you, My problem was not understanding how rally works. Now I have found target-interval setting so I can properly decrease this interval to match our use-case better. Currently running a race... @danielmitterdorfer - Have you considered having the option to dumping metrics to Elasticsearch _during_ the race so it is possible to follow the progress? This would be great for us. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [November 6, 2017, 9:06am UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/5 "2017-11-06T09:06:11Z")
This is tracked here: [https://github.com/elastic/rally/issues/217](https://github.com/elastic/rally/issues/217) ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [November 6, 2017, 9:25am UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/6 "2017-11-06T09:25:54Z")
> [@Christian\_Dahlqvist](#): > > This is tracked here: [Add ability to continuously stream metrics · Issue #217 · elastic/rally · GitHub](https://github.com/elastic/rally/issues/217) And this will be released with the next release 0.7.4. ---
**Author:** ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)\ **Post date:** [November 6, 2017, 9:48am UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/7 "2017-11-06T09:48:11Z")
Awesome! ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [November 8, 2017, 12:49pm UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/8 "2017-11-08T12:49:12Z")
Hi, we've just [released Rally 0.7.4](https://discuss.elastic.co/t/rally-0-7-4-released/106867) which contains the mentioned metrics streaming support. Daniel ---
**Author:** ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)\ **Post date:** [November 9, 2017, 10:49am UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/9 "2017-11-09T10:49:00Z")
Thanks, just installed the latest version and the metrics just keep coming 😉 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 7, 2017, 10:49am UTC](https://discuss.elastic.co/t/is-value-in-metrics-rally-metrics-index-aggregated/106034/10 "2017-12-07T10:49:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.