# Metricbeat is not capturing CPU and DISK information

**URL:** <https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [October 18, 2018, 9:30pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075 "2018-10-18T21:30:44Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [October 18, 2018, 9:30pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/1 "2018-10-18T21:30:45Z")

</div>

Hello Team,

I have enabled system module in metricbeat but all I see is Processora details in Elasticsearch but I don;t find anything CPU/CORE/DISK related information captured. any idea?

**system.yml**  
Dell-TMO-CT-Cass1:/root\>cat /etc/metricbeat/modules.d/system.yml

```auto
- module: system

  period: 10s
  metricsets:
    - cpu
    - load
    - memory
    - network
    - process
    - process_summary
    - core
    - diskio
    #- socket
  processes: ['.*']
  process.include_top_n:
    by_cpu: 5 # include top 5 processes by CPU
    by_memory: 5 # include top 5 processes by memory

- module: system
  period: 1m
  metricsets:
    - filesystem
    - fsstat
  processors:
  - drop_event.when.regexp:
      system.filesystem.mount_point: '^/(sys|cgroup|proc|dev|etc|host|lib)($|/)'

- module: system
  period: 15m
  metricsets:
    - uptime

**metricbeat.yml**
Dell-TMO-CT-Cass1:/root>cat /etc/metricbeat/metricbeat.yml | grep setup
setup.template.name: "cassandra-beats"
setup.template.pattern: "cas-beats-*"
setup.template.settings:
# options here, or by using the `-setup` CLI flag or the `setup` command.
#setup.dashboards.enabled: false
#setup.dashboards.url:
setup.kibana:
# `setup.kibana.host` options.

Dell-TMO-CT-Cass1:/root>cat /etc/metricbeat/metricbeat.yml | grep elastic -A10

#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["10.1.27.6:9200"]
  index: "logs_write_cas_beat"
  #template: "/etc/metricbeat/cass_beat_2.json"
  #template_name: "cassandra_beat"
  #template_overwrite: true

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"

```

Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\
**Post date:** [October 20, 2018, 5:59pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/2 "2018-10-20T17:59:24Z")

</div>

Hi @chandukreddi 🙂

Can you specify your metricbeat version and you OS? I guess is some kind of Linux

Best regards

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [October 26, 2018, 6:14pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/3 "2018-10-26T18:14:11Z")

</div>

Sorry Mario for delay.

beats: metricbeat-6.1.3-x86\_64.rpm  
OS: Red Hat Enterprise Linux Server release 7.4

Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [October 29, 2018, 3:01am UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/4 "2018-10-29T03:01:55Z")

</div>

Hello Experts,

Can anyone help me? I am new to metricsbeat and I stuck.

Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [October 29, 2018, 7:13pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/5 "2018-10-29T19:13:16Z")

</div>

@chandukreddi can you share one of the Elasticsearch documents that are being created in metricbeat? It'd be useful to see exactly which fields are being populated.

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 5, 2018, 11:01pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/6 "2018-11-05T23:01:11Z")

</div>

Hi Andrew,

Sorry, some reason I am not getting alerts when topic get updated.

Here you go!

{  
"\_index": "cas-beat-2018.10.17-000002",  
"\_type": "doc",  
"\_id": "vS-gy2YBhjpsdWfhvk22",  
"\_version": 1,  
"\_score": null,  
"\_source": {  
"@timestamp": "2018-10-31T20:20:45.784Z",  
"system": {  
"process": {  
"pgid": 74076,  
"cmdline": "python /usr/local/dse-5.0.14/resources/cassandra/bin/cqlsh.py",  
"cwd": "/root",  
"fd": {  
"open": 8,  
"limit": {  
"soft": 120000,  
"hard": 120000  
}  
},  
"state": "sleeping",  
"username": "root",  
"cpu": {  
"total": {  
"pct": 0.004,  
"norm": {  
"pct": 0.0001  
}  
},  
"start\_time": "2018-10-31T19:49:22.000Z"  
},  
"ppid": 70795,  
"name": "python",  
"memory": {  
"size": 550658048,  
"rss": {  
"bytes": 35090432,  
"pct": 0.0003  
},  
"share": 4681728  
},  
"pid": 74076  
}  
},  
"metricset": {  
"module": "system",  
"name": "process",  
"rtt": 83020  
},  
"beat": {  
"name": "localhost.localdomain",  
"hostname": "localhost.localdomain",  
"version": "6.1.3"  
}  
},  
"fields": {  
"@timestamp": [  
"2018-10-31T20:20:45.784Z"  
],  
"system.process.cpu.start\_time": [  
"2018-10-31T19:49:22.000Z"  
]  
},  
"sort": [  
1541017245784  
]  
}

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 7, 2018, 10:40pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/7 "2018-11-07T22:40:02Z")

</div>

@Andrew_Cholakian1, Could you please help me?

Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [November 7, 2018, 11:43pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/8 "2018-11-07T23:43:45Z")

</div>

So, the filesystem metricset in your config is configured to only send events once per minute. That means only some events will have filesystem data.

You can read more about that here.

In the document you shared I do see CPU stats, so that seems to be working correctly.

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 8, 2018, 7:22pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/9 "2018-11-08T19:22:12Z")

</div>

Thanks Andrew!

In case your referring to below lines, I believe that is related to that particular process right?

I am looking for overall host CPU usage and LOAD, on top that it also missing diskio, if you look at overall document it just captured only system module process info.

"system": {  
"process": {

process:  
"pgid": 74076,  
"cmdline": "python /usr/local/dse-5.0.14/resources/cassandra/bin/cqlsh.py",

"cpu": {  
"total": {  
"pct": 0.004,  
"norm": {  
"pct": 0.0001  
}  
},  
"start\_time": "2018-10-31T19:49:22.000Z"  
},

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [November 8, 2018, 8:26pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/10 "2018-11-08T20:26:38Z")

</div>

It looks like you're on windows, but windows doesn't offer a load statistic.

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 8, 2018, 10:09pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/11 "2018-11-08T22:09:33Z")

</div>

Hi Andrew,

its not windows, its Linux.

Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [November 9, 2018, 12:33am UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/12 "2018-11-09T00:33:04Z")

</div>

Do you have the system load metricset enabled? [https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-metricset-system-load.html](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-metricset-system-load.html)

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 9, 2018, 5:53pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/13 "2018-11-09T17:53:40Z")

</div>

Hi @Andrew_Cholakian1,

Yes I have enabled on sytem.yml file, Do I need to enable anywhere else? and I do see those fields in my Kibana when I disable option hide missing fields, this means its enabled but not capturing any data.

--- System module parameters

- module: system

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 19, 2018, 4:33pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/14 "2018-11-19T16:33:48Z")

</div>

@all , Can anyone help me to understand why I can't see Load/CPU/DISK IO info in elasticsearch docs?

Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [November 19, 2018, 4:39pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/15 "2018-11-19T16:39:56Z")

</div>

Hmmm, it should be showing up. I'm not sure why it isn't. @ruflin or @shaunak do you have any ideas here?

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [November 19, 2018, 4:57pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/16 "2018-11-19T16:57:05Z")

</div>

Yes, it's odd that it's not showing up.

@chandukreddi Could you try the following (temporarily for debugging purposes only) to help and narrow down the issue?

1. Disable all modules except `system`.
2. Edit your `./modules.d/system.yml` and only enable the `cpu` metricset.
3. Start up Metricbeat but with the `-e -d"*"` flags. This will generate debugging output. Could you please post this here? Just the first 10 seconds or so of output should be sufficient.

Thanks,

Shaunak

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 19, 2018, 5:07pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/17 "2018-11-19T17:07:15Z")

</div>

Okay @shaunak let me try that.

Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 19, 2018, 5:23pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/18 "2018-11-19T17:23:53Z")

</div>

Hi @shaunak  
2018/11/19 22:47:16.180010 wrapper.go:149: DBG [module] Starting metricSetWrapper[module=system, name=diskio, host=]  
2018/11/19 22:47:16.350588 processor.go:275: DBG [publish] Publish event: {  
"@timestamp": "2018-11-19T22:47:16.180Z",  
"@metadata": {  
"beat": "metricbeat",  
"type": "doc",  
"version": "6.1.3"  
},  
"system": {  
"diskio": {  
"name": "sdg",  
"read": {  
"count": 137,  
"time": 20,  
"bytes": 2334720  
},  
"write": {  
"bytes": 0,  
"count": 0,  
"time": 0  
},  
"io": {  
"time": 17  
},  
"iostat": {  
"service\_time": 0,  
"busy": 0,  
"read": {  
"request": {  
"merges\_per\_sec": 0,  
"per\_sec": 0  
},  
"per\_sec": {  
"bytes": 0  
}  
},  
"write": {  
"request": {  
"merges\_per\_sec": 0,  
"per\_sec": 0  
},  
"per\_sec": {  
"bytes": 0  
}  
},  
"queue": {  
"avg\_size": 0  
},  
"request": {  
"avg\_size": 0  
},  
"await": 0  
},  
"serial\_number": "36d094660757264002333866362b40e36"  
}  
},  
"metricset": {  
"module": "system",  
"name": "diskio",  
"rtt": 170174  
},  
"beat": {  
"name": "localhost.localdomain",  
"hostname": "localhost.localdomain",  
"version": "6.1.3"  
}  
}  
Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 19, 2018, 5:24pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/19 "2018-11-19T17:24:44Z")

</div>

My System module.  
Dell-TMO-CT-Cass1:/root\>cat /etc/metricbeat/modules.d/system.yml

- module: system

# - load

# - memory

# - network

# - process

# - process\_summary

# - core

# - diskio

```
#- socket

```

processes: ['.\*']  
process.include\_top\_n:  
by\_cpu: 5 # include top 5 processes by CPU  
by\_memory: 5 # include top 5 processes by memory

- module: system  
period: 1m  
metricsets:

- module: system  
period: 15m  
metricsets:

Thanks  
Chandra

---

<div class="post-metadata">

**Author:** ![chandukreddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandukreddi/32/29241_2.png) [@chandukreddi](https://discuss.elastic.co/u/chandukreddi)\
**Post date:** [November 19, 2018, 5:32pm UTC](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075/20 "2018-11-19T17:32:37Z")

</div>

Here is the CPU module stats

2018/11/19 22:47:15.825514 wrapper.go:149: DBG [module] Starting metricSetWrapper[module=system, name=cpu, host=]  
2018/11/19 22:47:15.828325 processor.go:275: DBG [publish] Publish event: {  
"@timestamp": "2018-11-19T22:47:15.825Z",  
"@metadata": {  
"beat": "metricbeat",  
"type": "doc",  
"version": "6.1.3"  
},  
"system": {  
"cpu": {  
"irq": {  
"pct": 0  
},  
"softirq": {  
"pct": 0  
},  
"user": {  
"pct": 0  
},  
"idle": {  
"pct": 0  
},  
"steal": {  
"pct": 0  
},  
"system": {  
"pct": 0  
},  
"iowait": {  
"pct": 0  
},  
"total": {  
"pct": 0  
},  
"nice": {  
"pct": 0  
},  
"cores": 32  
}  
},  
"metricset": {  
"name": "cpu",  
"rtt": 2472,  
"module": "system"  
},  
"beat": {  
"name": "localhost.localdomain",  
"hostname": "localhost.localdomain",  
"version": "6.1.3"  
}  
}

Thanks  
Chandra

[Next page](https://discuss.elastic.co/t/metricbeat-is-not-capturing-cpu-and-disk-information/153075.md?page=2)
