# System module period **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [February 21, 2017, 4:54pm UTC](https://discuss.elastic.co/t/system-module-period/75923 "2017-02-21T16:54:31Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Exocomp](https://avatars.discourse-cdn.com/v4/letter/e/ea5d25/32.png) [@Exocomp](https://discuss.elastic.co/u/Exocomp)\ **Post date:** [February 21, 2017, 4:54pm UTC](https://discuss.elastic.co/t/system-module-period/75923/1 "2017-02-21T16:54:31Z")
I'm using version 5.2.1 on Win10-x64, the metricbeat.yml is setup with a period of 10s see below, outputting to elasticsearch but the log shows the logging period always 30 seconds, I'm a new user what am I missing ? metricbeat.exe -version metricbeat version 5.2.1 (amd64), libbeat 5.2.1 **metricbeat.yml** ``` #------------------------------- System Module ------------------------------- - module: system metricsets: - cpu - filesystem - fsstat - memory - network - process enabled: true period: 10s processes: ['.*'] ``` **Log** : C:\Users\Win10-x64\Downloads\metricbeat-5.2.1-windows-x86\_64\> **metricbeat.exe -e** 2017/02/21 16:51:59.940291 beat.go:267: INFO Home path: [C:\Users\Win10-x64\Downloads\metricbeat-5.2.1-windows-x86\_64] Config path: [C:\Users\Win10-x64\Downloads\metricbeat-5.2.1-windows-x86\_64] Data path: [C:\Users\Win10-x64\Downloads\metricbeat-5.2.1-windows-x86\_64\data] Logs path: [C:\Users\Win10-x64\Downloads\metricbeat-5.2.1-windows-x86\_64\logs] 2017/02/21 16:51:59.942295 beat.go:177: INFO Setup Beat: metricbeat; Version: 5.2.1 2017/02/21 16:51:59.942295 output.go:167: INFO Loading template enabled. Reading template file: C:\Users\Win10-x64\Downloads\metricbeat-5.2.1-windows-x86\_64\metricbeat.template.json 2017/02/21 16:51:59.944294 output.go:178: INFO Loading template enabled for Elasticsearch 2.x. Reading template file: C:\Users\Win10-x64\Downloads\metricbeat-5.2.1-windows-x86\_64\metricbeat.template-es2x.json 2017/02/21 16:51:59.947303 client.go:120: INFO Elasticsearch url: [http://192.168.1.121:9200](http://192.168.1.121:9200) 2017/02/21 16:51:59.947303 outputs.go:106: INFO Activated elasticsearch as output plugin. 2017/02/21 16:51:59.947303 publish.go:291: INFO Publisher name: DESKTOP-FKLSK0G 2017/02/21 16:51:59.949247 logp.go:219: **INFO Metrics logging every 30s** 2017/02/21 16:51:59.950317 async.go:63: INFO Flush Interval set to: 1s 2017/02/21 16:51:59.951335 async.go:64: INFO Max Bulk Size set to: 50 Thanks, E ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [February 22, 2017, 4:29am UTC](https://discuss.elastic.co/t/system-module-period/75923/2 "2017-02-22T04:29:47Z")
That message is about how ofter the logger writes metrics to the log. It has nothing to do with the collection period of the system module. It would be better to look at the elapsed time between cpu events that have been written to Elasticsearch. ---
**Author:** ![Exocomp](https://avatars.discourse-cdn.com/v4/letter/e/ea5d25/32.png) [@Exocomp](https://discuss.elastic.co/u/Exocomp)\ **Post date:** [February 24, 2017, 9:33pm UTC](https://discuss.elastic.co/t/system-module-period/75923/3 "2017-02-24T21:33:53Z")
Your right I got confused, is there a way to change the logging period, I guess 30 seconds is decent enough if not. ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [February 25, 2017, 6:59pm UTC](https://discuss.elastic.co/t/system-module-period/75923/4 "2017-02-25T18:59:36Z")
See the [documentation](https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-logging.html#_metrics_period) for logging. There is a configurable metrics period. ---
**Author:** ![Exocomp](https://avatars.discourse-cdn.com/v4/letter/e/ea5d25/32.png) [@Exocomp](https://discuss.elastic.co/u/Exocomp)\ **Post date:** [February 26, 2017, 1:54pm UTC](https://discuss.elastic.co/t/system-module-period/75923/5 "2017-02-26T13:54:13Z")
That's what got me confused in the first place, I see that the metrics period is configurable. I was referring to the logging period. ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [February 27, 2017, 11:57pm UTC](https://discuss.elastic.co/t/system-module-period/75923/6 "2017-02-27T23:57:14Z")
What do you find confusing about the logging documentation so that it can be improved? Have you looked at the `metricbeat.full.yml` file that is provided in the download package? It contains an full example config with all of the options. In there you should see a commented out example line setting the `logging.metrics.period` to its default value of `30s`. `logging.metrics.period: 30s` You can lower that value if you would like the logger to write out the values more often. To be clear, these are internal metrics about the Metricbeat process, not metrics that were collected by Metricbeat from the system or other processes. ---
**Author:** ![Exocomp](https://avatars.discourse-cdn.com/v4/letter/e/ea5d25/32.png) [@Exocomp](https://discuss.elastic.co/u/Exocomp)\ **Post date:** [February 28, 2017, 12:11am UTC](https://discuss.elastic.co/t/system-module-period/75923/7 "2017-02-28T00:11:17Z")
I didn't know, thanks for enlightening me, I appreciate it. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 28, 2017, 12:11am UTC](https://discuss.elastic.co/t/system-module-period/75923/8 "2017-03-28T00:11:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.