# Transaction command equivalent in ELK

**URL:** <https://discuss.elastic.co/t/transaction-command-equivalent-in-elk/86653>\
**Category:** Elasticsearch\
**Created:** [May 22, 2017, 10:32am UTC](https://discuss.elastic.co/t/transaction-command-equivalent-in-elk/86653 "2017-05-22T10:32:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\
**Post date:** [May 22, 2017, 10:32am UTC](https://discuss.elastic.co/t/transaction-command-equivalent-in-elk/86653/1 "2017-05-22T10:32:44Z")

</div>

We want to get the total time taken by a transaction (Log analysis). transaction command in Splunk gives two fields duration and eventcount when the transaction command has been used. How this can be achieved in ELK stack?

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [May 22, 2017, 11:20am UTC](https://discuss.elastic.co/t/transaction-command-equivalent-in-elk/86653/2 "2017-05-22T11:20:31Z")

</div>

See "entity centric indexing" [https://www.youtube.com/watch?v=yBf7oeJKH2Y](https://www.youtube.com/watch?v=yBf7oeJKH2Y)

---

<div class="post-metadata">

**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\
**Post date:** [June 16, 2017, 4:53am UTC](https://discuss.elastic.co/t/transaction-command-equivalent-in-elk/86653/3 "2017-06-16T04:53:29Z")

</div>

Thanks. This would need changing the time series indexing - the daily indexing structure. Is there way to accomplish using the daily log indexing index structure.

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [June 16, 2017, 6:45am UTC](https://discuss.elastic.co/t/transaction-command-equivalent-in-elk/86653/4 "2017-06-16T06:45:30Z")

</div>

> [@mruthyu](#):
>
> This would need changing the time series indexing

In the video I am talking about creating an ancillary index alongside your usual time series log index - that does not go away.

If you are talking about organising your entity index into time-based indices to help deal with purging old transactions, your code will need to deal with scenarios where transactions span the time boundary you choose for grouping entity indexes.

---

<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, 2017, 6:45am UTC](https://discuss.elastic.co/t/transaction-command-equivalent-in-elk/86653/5 "2017-07-14T06:45:51Z")

</div>

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