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？
Are there any errors in the Metricbeat log? What if you enable debug logging with:
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]?
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
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
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.