# Does initial interval work on start up for google workspace module?

**URL:** https://discuss.elastic.co/t/does-initial-interval-work-on-start-up-for-google-workspace-module/300701
**Category:** Beats
**Tags:** docker, filebeat
**Created:** [March 25, 2022, 1:29pm UTC](https://discuss.elastic.co/t/does-initial-interval-work-on-start-up-for-google-workspace-module/300701 "2022-03-25T13:29:05Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)
#### Post date: [March 25, 2022, 1:29pm UTC](https://discuss.elastic.co/t/does-initial-interval-work-on-start-up-for-google-workspace-module/300701/1 "2022-03-25T13:29:05Z")

</div>

Hello.

I would like to ask question for [google workspace module](https://www.elastic.co/guide/en/beats/filebeat/7.17/filebeat-module-google_workspace.html#filebeat-module-google_workspace) .

Doc says , filebeat will poll up to `var.initial_interval` when the filebeat starts.

> It will poll events up to this time period when the module starts.

However, I have used [fresh docker image](https://hub.docker.com/layers/filebeat/elastic/filebeat/7.17.1/images/sha256-b0491ef0c9bb5c8ae315e450ba00d065fd4458f009ff7f61750830d82c8ba476?context=explore) and started up but only polled up to `var.interval` .

I have looked at [the code](https://github.com/elastic/beats/blob/v7.17.1/x-pack/filebeat/module/google_workspace/drive/config/config.yml#L20) and it seems that `var.initial_interval` is used as _default_ which is only used when [value is empty or the template parsing fails](https://www.elastic.co/guide/en/beats/filebeat/7.17/filebeat-input-httpjson.html#_set) . Which I understood as `var.initial_interval` is not used unless something is wrong with _value_ .

Should I go with _the doc_ or should I trust the code ?

Thanks ,  
Yu

---

<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: [March 29, 2022, 12:38pm UTC](https://discuss.elastic.co/t/does-initial-interval-work-on-start-up-for-google-workspace-module/300701/2 "2022-03-29T12:38:33Z")

</div>

So the code shows that since the`.cursor.*` is empty when the coffee first runs it does use the initial interval to poll. Then the cursor is updated and is used for subsequent API calls.

---

<div class="post-metadata">

### Author: ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)
#### Post date: [March 30, 2022, 10:11am UTC](https://discuss.elastic.co/t/does-initial-interval-work-on-start-up-for-google-workspace-module/300701/3 "2022-03-30T10:11:06Z")

</div>

@legoguy1000  
Thank you for the reply. Yeah your right. I was wrong.  
Just tested again with DEBUG level log and confirmed that `var.initial_interval` is used.

```auto
2022-03-30T10:04:22.580Z DEBUG [input.httpjson-cursor.retryablehttp] go-retryablehttp@v0.6.6/client.go:504 performing request%!(EXTRA string=method, string=GET, string=url, *url.URL=https://www.googleapis.com/admin/reports/v1/activity/users/all/applications/drive?startTime=2022-03-26T10%3A04%3A22Z) {"id": "BBFA557C8D443451", "input_source": "https://www.googleapis.com/admin/reports/v1/activity/users/all/applications/drive", "input_url": "https://www.googleapis.com/admin/reports/v1/activity/users/all/applications/drive"}

```

---

<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: [April 27, 2022, 12:11pm UTC](https://discuss.elastic.co/t/does-initial-interval-work-on-start-up-for-google-workspace-module/300701/4 "2022-04-27T12:11:50Z")

</div>

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