# Field for http response times

**URL:** <https://discuss.elastic.co/t/field-for-http-response-times/272742>\
**Category:** Logs\
**Tags:** ecs-elastic-common-schema\
**Created:** [May 11, 2021, 8:46pm UTC](https://discuss.elastic.co/t/field-for-http-response-times/272742 "2021-05-11T20:46:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sergii\_Ovcharenko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sergii_ovcharenko/32/88625_2.png) [@Sergii\_Ovcharenko](https://discuss.elastic.co/u/Sergii_Ovcharenko)\
**Post date:** [May 11, 2021, 8:46pm UTC](https://discuss.elastic.co/t/field-for-http-response-times/272742/1 "2021-05-11T20:46:35Z")

</div>

Hey,

Our app logs HTTP response times for the APIs we provide. What would be the best standard field to put this data in to follow ECS standard and best practices? There is no `http.response.latency` or similar field and `event.*` fields look like an overkill.

Thank you.

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [May 12, 2021, 4:51am UTC](https://discuss.elastic.co/t/field-for-http-response-times/272742/2 "2021-05-12T04:51:35Z")

</div>

For the current ECS spec I would say `event.duration` with `start` and `end` are the most applicable fields to use.

---

<div class="post-metadata">

**Author:** ![ebeahan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebeahan/32/78989_2.png) [@ebeahan](https://discuss.elastic.co/u/ebeahan)\
**Post date:** [May 12, 2021, 5:04pm UTC](https://discuss.elastic.co/t/field-for-http-response-times/272742/3 "2021-05-12T17:04:44Z")

</div>

Welcome to the community, @Sergii_Ovcharenko!

I agree with @legoguy1000 that `event.duration` could map well to something like `$request_time` from NGINX (noting the necessary value conversion from milliseconds to nanoseconds).

If `event.duration` doesn't align with your need, custom fields can be used alongside ECS fields, and if you follow the [recommended guidance](https://www.elastic.co/guide/en/ecs/current/ecs-custom-fields-in-ecs.html#_modeling_to_reduce_chances_of_conflict) you minimize the risk of any future field name conflicts.

---

<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:** [June 9, 2021, 5:05pm UTC](https://discuss.elastic.co/t/field-for-http-response-times/272742/4 "2021-06-09T17:05:27Z")

</div>

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