# Telemetry Devices and Rally 2.7.0

**URL:** <https://discuss.elastic.co/t/telemetry-devices-and-rally-2-7-0/326638>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [February 28, 2023, 12:50am UTC](https://discuss.elastic.co/t/telemetry-devices-and-rally-2-7-0/326638 "2023-02-28T00:50:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Safty](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/safty/32/112921_2.png) [@Safty](https://discuss.elastic.co/u/Safty)\
**Post date:** [February 28, 2023, 12:50am UTC](https://discuss.elastic.co/t/telemetry-devices-and-rally-2-7-0/326638/1 "2023-02-28T00:50:29Z")

</div>

Hello, fellow elastic/rally kids.

Does Rally 2.7.0 support Telemetry Devices? If so is the expectation that all tracks are supported? Meaning you can run any telemetry devices listed under 'esrally list telemetry'. (the special conditions around `jit` , `gc` , `jfr` stats notwithstanding)

The example in the rally documentation calls out specifically "esrally race --track=pmc --telemetry jfr". Given there are more than just the 'jfr' telemetry devices available and there are other tracks beyond 'pmc' I figured it would work with others. However I have not been able to get any results generated with say "esrally race --track=nyc\_taxis --telemetry node-stats" for instance.

Before I start devoting time digging into what might be going on, I figured I would check first.

Thank you.

---

<div class="post-metadata">

**Author:** ![Evgenia\_Badiyanova](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/evgenia_badiyanova/32/84068_2.png) [@Evgenia\_Badiyanova](https://discuss.elastic.co/u/Evgenia_Badiyanova)\
**Post date:** [February 28, 2023, 1:51am UTC](https://discuss.elastic.co/t/telemetry-devices-and-rally-2-7-0/326638/2 "2023-02-28T01:51:06Z")

</div>

Hello @Safty! Thank you for using Rally!

Telemetry devices are supported for all tracks.

All the `*-stats` telemetry devices and [node-stats](https://esrally.readthedocs.io/en/stable/telemetry.html#node-stats) specifically records metrics and sends them to metric store. So if you haven't already, please make sure you set up a dedicated metrics store ([docs link](https://esrally.readthedocs.io/en/stable/configuration.html#reporting)). You will then find captured node stats in the `rally-metrics-*` indices in documents where `"name"` is `"node-stats"`.

Thanks,  
Evgenia

---

<div class="post-metadata">

**Author:** ![Bradley\_Deam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bradley_deam/32/52991_2.png) [@Bradley\_Deam](https://discuss.elastic.co/u/Bradley_Deam)\
**Post date:** [February 28, 2023, 1:55am UTC](https://discuss.elastic.co/t/telemetry-devices-and-rally-2-7-0/326638/3 "2023-02-28T01:55:18Z")

</div>

> [@Safty](#):
>
> esrally race --track=nyc\_taxis --telemetry node-stats

Hi @Safty, thanks for your interest in Rally 🙂

> Does Rally 2.7.0 support Telemetry Devices? If so is the expectation that all tracks are supported? Meaning you can run any telemetry devices listed under 'esrally list telemetry'.

For the most part, yes. Some telemetry devices might not work with older versions of Elasticsearch if an API wasn't available (e.g. the `disk-usage-stats` telemetry device won't work on clusters prior to \<7.15 because the API doesn't exist).

> The example in the rally documentation calls out specifically "esrally race --track=pmc --telemetry jfr". Given there are more than just the 'jfr' telemetry devices available and there are other tracks beyond 'pmc' I figured it would work with others. However I have not been able to get any results generated with say "esrally race --track=nyc\_taxis --telemetry node-stats" for instance.

By default Rally uses an 'in-memory' metrics store to collect and store race metrics. The results summary presented at the end of a race is calculated off of these metrics stored in-memory. We don't currently summarise the metrics returned from `node-stats`, which is a roundabout way of saying that I don't think the docs make it clear that we assume you have a [remote metrics store](https://esrally.readthedocs.io/en/stable/metrics.html) setup under `[reporting]` in `~/.rally/rally.ini` in order to analyse the output of some telemetry devices (including `node-stats`).

---

<div class="post-metadata">

**Author:** ![Safty](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/safty/32/112921_2.png) [@Safty](https://discuss.elastic.co/u/Safty)\
**Post date:** [February 28, 2023, 3:57pm UTC](https://discuss.elastic.co/t/telemetry-devices-and-rally-2-7-0/326638/4 "2023-02-28T15:57:32Z")

</div>

Hello,

Ah! Thank you for the clarification regarding the in-memory and remote metric store configurations. I will have a look at the documentation referenced regarding remote metric store set up.

Thank you.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 28, 2023, 3:58pm UTC](https://discuss.elastic.co/t/telemetry-devices-and-rally-2-7-0/326638/5 "2023-03-28T15:58:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.