# Changing epoch timeout in SumStats

**URL:** https://community.zeek.org/t/changing-epoch-timeout-in-sumstats/5349
**Category:** Development
**Tags:** development
**Created:** [June 11, 2018, 10:25pm UTC](https://community.zeek.org/t/changing-epoch-timeout-in-sumstats/5349 "2018-06-11T22:25:33Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Jim\_Mellander](https://avatars.discourse-cdn.com/v4/letter/j/e47c2d/32.png) [@Jim\_Mellander](https://community.zeek.org/u/Jim_Mellander)
#### Post date: [June 11, 2018, 10:25pm UTC](https://community.zeek.org/t/changing-epoch-timeout-in-sumstats/5349/1 "2018-06-11T22:25:33Z")

</div>

Hi all:

I’m working on a statistics gathering script using sumstats. I would dearly love to have it synchronized with the log rotation interval. This means that the first epoch interval would most likely be short, with future epochs being at the rotation interval. Prior Bros (2.5.2) had an intriguing comment about possible on-demand call for sumstats, which doesn’t seem to be in the latest master.

So, at the moment, what I’m looking for is one of the two options:

1. Allow for a pure ‘on-demand’ option for sumstats results, allowing the user script to manage the results, or
2. Allow redefining the epoch timeout on the fly.

Option 3 is hacking on the sumstats code…

Any comments?

---

<div class="post-metadata">

### Author: ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)
#### Post date: [May 6, 2022, 3:45pm UTC](https://community.zeek.org/t/changing-epoch-timeout-in-sumstats/5349/2 "2022-05-06T15:45:52Z")

</div>


