# Metricbeat6.0 system module doesn't capture linux system process **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [November 22, 2017, 7:09am UTC](https://discuss.elastic.co/t/metricbeat6-0-system-module-doesnt-capture-linux-system-process/108654 "2017-11-22T07:09:26Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![shiloong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shiloong/32/44625_2.png) [@shiloong](https://discuss.elastic.co/u/shiloong)\ **Post date:** [November 22, 2017, 7:09am UTC](https://discuss.elastic.co/t/metricbeat6-0-system-module-doesnt-capture-linux-system-process/108654/1 "2017-11-22T07:09:27Z")
I'm recently use metricbeat to monitor my server；and I found as default in Linux platform metricbeat system module doesn't capture the system process there cmdline always like this _[xxxx]_ ,I haven't found them from the records in ES. I wonder am I right？ ---
**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:** [November 22, 2017, 9:13pm UTC](https://discuss.elastic.co/t/metricbeat6-0-system-module-doesnt-capture-linux-system-process/108654/2 "2017-11-22T21:13:20Z")
Are there any errors in the Metricbeat log? What if you enable debug logging with: ```auto logging.level: debug logging.selectors: ["system.process"] ``` Can you give more details on the processes that are problematic? Are the contents of `/proc/[PID]/cmdline` literally `[xxxx]`? ---
**Author:** ![shiloong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shiloong/32/44625_2.png) [@shiloong](https://discuss.elastic.co/u/shiloong)\ **Post date:** [November 23, 2017, 1:47am UTC](https://discuss.elastic.co/t/metricbeat6-0-system-module-doesnt-capture-linux-system-process/108654/3 "2017-11-23T01:47:10Z")
It's all kernel process like this: > 11 root rt 0 0 0 0 S 0.0 0.0 0:30.50 watchdog/0 > 12 root rt 0 0 0 0 S 0.0 0.0 0:31.35 watchdog/1 > 13 root rt 0 0 0 0 S 0.0 0.0 0:19.37 migration/1 > 14 root 20 0 0 0 0 S 0.0 0.0 1:25.61 ksoftirqd/1 > 17 root rt 0 0 0 0 S 0.0 0.0 0:30.54 watchdog/2 > 18 root rt 0 0 0 0 S 0.0 0.0 0:13.83 migration/2 > 19 root 20 0 0 0 0 S 0.0 0.0 1:23.05 ksoftirqd/2 > 22 root rt 0 0 0 0 S 0.0 0.0 0:30.50 watchdog/3 > 23 root rt 0 0 0 0 S 0.0 0.0 0:14.64 migration/3 and I enabled debug log found nothing useful, there nothing about these process ---
**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:** [November 23, 2017, 2:51pm UTC](https://discuss.elastic.co/t/metricbeat6-0-system-module-doesnt-capture-linux-system-process/108654/4 "2017-11-23T14:51:32Z")
You are running Metricbeat as root? If so please open an issue on Github for this. Sounds like there's an issue. [https://github.com/elastic/beats/issues/new](https://github.com/elastic/beats/issues/new) ---
**Author:** ![shiloong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shiloong/32/44625_2.png) [@shiloong](https://discuss.elastic.co/u/shiloong)\ **Post date:** [November 24, 2017, 1:26am UTC](https://discuss.elastic.co/t/metricbeat6-0-system-module-doesnt-capture-linux-system-process/108654/5 "2017-11-24T01:26:38Z")
Yes, I run it as root. And I had opened an issue [https://github.com/elastic/beats/issues/5700](https://github.com/elastic/beats/issues/5700) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 22, 2017, 1:26am UTC](https://discuss.elastic.co/t/metricbeat6-0-system-module-doesnt-capture-linux-system-process/108654/6 "2017-12-22T01:26:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.