-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impossible to get "system.process.cpu.total.ticks" field #3590
Labels
Comments
Thanks for the report. Looking briefly over the code, it seems that the process metricset has support for "ticks", but the configuration setting is never actually checked. |
Is this bug planned to be assigned/fixed in a futur version? |
@OlivierPT Definitively. We will try to look into this in more detail soonish. |
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Mar 20, 2017
When `cpu_ticks` is true in the config file, the system process metricset will report the number of “ticks” (actually jiffies on linux) used in user space (`system.process.cpu.user`), system (`system.process.cpu.system`), and total (`system.process.cpu.total.ticks`). Fixes elastic#3590
I opened a PR to fix this: #3776 |
ruflin
pushed a commit
that referenced
this issue
Mar 21, 2017
When `cpu_ticks` is true in the config file, the system process metricset will report the number of “ticks” (actually jiffies on linux) used in user space (`system.process.cpu.user`), system (`system.process.cpu.system`), and total (`system.process.cpu.total.ticks`). Fixes #3590
monicasarbu
pushed a commit
to monicasarbu/beats
that referenced
this issue
Mar 29, 2017
…3776) When `cpu_ticks` is true in the config file, the system process metricset will report the number of “ticks” (actually jiffies on linux) used in user space (`system.process.cpu.user`), system (`system.process.cpu.system`), and total (`system.process.cpu.total.ticks`). Fixes elastic#3590 (cherry picked from commit 92fa6c4)
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Apr 12, 2017
…3776) When `cpu_ticks` is true in the config file, the system process metricset will report the number of “ticks” (actually jiffies on linux) used in user space (`system.process.cpu.user`), system (`system.process.cpu.system`), and total (`system.process.cpu.total.ticks`). Fixes elastic#3590 (cherry picked from commit 92fa6c4)
ruflin
pushed a commit
that referenced
this issue
Apr 12, 2017
…4005) When `cpu_ticks` is true in the config file, the system process metricset will report the number of “ticks” (actually jiffies on linux) used in user space (`system.process.cpu.user`), system (`system.process.cpu.system`), and total (`system.process.cpu.total.ticks`). Fixes #3590 (cherry picked from commit 92fa6c4)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems like there is no way to activate the "system.process.cpu.total.ticks" field with Metricbeat. Tested with version 5.1.2 and 5.2.0, the "cpu_ticks" option doesn't work. It only adds ticks information in "cpu" and "core" modules events.
Either the option should also activate the fields for "process" module, either we need an additional option.
The text was updated successfully, but these errors were encountered: