# Metric beat system metrics
**URL:** https://discuss.elastic.co/t/metric-beat-system-metrics/118177
**Category:** Beats
**Tags:** metricbeat
**Created:** [February 2, 2018, 7:44am UTC](https://discuss.elastic.co/t/metric-beat-system-metrics/118177 "2018-02-02T07:44:22Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ravitandur](https://discuss.elastic.co/u/ravitandur)
#### Post date: [February 2, 2018, 7:44am UTC](https://discuss.elastic.co/t/metric-beat-system-metrics/118177/1 "2018-02-02T07:44:22Z")
I am using metric beat to get the system metrics using system module.
I started the metric beat on all required nodes and metric data is coming properly to elastic search and able to see the data using default dashboards provided.
My question:
On one of the server, I increased CPU cores from 4 to 8, but metric beat is still sending the old value [4].
When I restart the metric beat after increasing the CPU cores it is sending the correct value.
Can you please let me know why do I need to restart the metric beat after changing the cores, does metric beat can't pickup the latest cpu cores?
Thanks,
Ravi
---
### Author:  [@adrisr](https://discuss.elastic.co/u/adrisr)
#### Post date: [February 2, 2018, 5:13pm UTC](https://discuss.elastic.co/t/metric-beat-system-metrics/118177/2 "2018-02-02T17:13:19Z")
You're correct. Metricbeat needs to be restarted for the new number of CPU cores to be picked up.
Opened an issue to fix it:
>
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 2, 2018, 5:19pm UTC](https://discuss.elastic.co/t/metric-beat-system-metrics/118177/3 "2018-03-02T17:19:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.