# RUM navigation timings

**URL:** <https://discuss.elastic.co/t/rum-navigation-timings/236744>\
**Category:** APM\
**Tags:** rum\
**Created:** [June 11, 2020, 4:10pm UTC](https://discuss.elastic.co/t/rum-navigation-timings/236744 "2020-06-11T16:10:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![moixcruz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moixcruz/32/40464_2.png) [@moixcruz](https://discuss.elastic.co/u/moixcruz)\
**Post date:** [June 11, 2020, 4:10pm UTC](https://discuss.elastic.co/t/rum-navigation-timings/236744/1 "2020-06-11T16:10:44Z")

</div>

Hi! This is more a generic question wondering if anyone can point me with best solution to achieve what we are trying to do, hope nothing so crazy 😉

First of all our stack is elastic-apm and rum, at the moment running apm-server, logstash (in between elastic-servers and elasticsearch), elasticsearch and kibana on v7.5.1  
rum agents are still on 4.1.2, but planing upgrading them shortly to latest 5.x

We use it daily for troubleshooting and performance analysis, now I'm trying to create some simplified dashboards (in grafana) to have highlevel navigationTiming metrics for the instrumented domains.

I don't want to put so many times that are hard to read but simply some highlighting network, backend and frontend so a quick view tell how good is performing. Following image is very descriptive:

 ![tming1](https://us1.discourse-cdn.com/elastic/original/3X/2/2/22a702e49319a28f80f873600ead52c01eda9c8a.png)

which could be directly translated in terms of navigation timing model marks that elastic rum has:

 ![timing-overview](https://us1.discourse-cdn.com/elastic/original/3X/c/d/cdf7a444668af802013b250332ffad11e5e97b31.png)

But RUM agent (at least our current version 4.1.2) only contain some of them:  
transaction.marks.agent.domComplete  
transaction.marks.agent.domInteractive  
transaction.marks.agent.renderTime  
transaction.marks.agent.timeToFirstByte

What should be the best approach to have other marks such as:

DNS.time = domainLookupEnd- domainLookupStart  
Connect.time = connectEnd - connectStart  
Backend.time = responseEnd - requestStart  
Receive.time = responseEnd - responseStart  
. . .

Should those be calculated by rum agent? are plans for something like this?

Thanks in advance?

---

<div class="post-metadata">

**Author:** ![vigneshh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vigneshh/32/35767_2.png) [@vigneshh](https://discuss.elastic.co/u/vigneshh)\
**Post date:** [June 23, 2020, 10:53am UTC](https://discuss.elastic.co/t/rum-navigation-timings/236744/2 "2020-06-23T10:53:36Z")

</div>

Hi @moixcruz,

Copying over from GitHub.

RUM agent already captures some of these metrics as part of [Breakdown metrics](https://www.elastic.co/guide/en/apm/agent/rum-js/current/breakdown-metrics-docs.html)

You would need to enable the `breakdownMetrics: true` in the [configuration](https://www.elastic.co/guide/en/apm/agent/rum-js/current/configuration.html#breakdown-metrics) which requires APM Server and Kibana \>= 7.4 version.

Let us know if it helps your use case.

Thanks,  
Vignesh

---

<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:** [July 14, 2020, 7:08am UTC](https://discuss.elastic.co/t/rum-navigation-timings/236744/3 "2020-07-14T07:08:29Z")

</div>

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