| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Manage this branch in SquashTest this branch here: https://hexchainproc-plugin-psi-w3rzz.squash.io |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Approving changes to the files for which I am the code owner.
Sorry, something went wrong.
Yes
I don't know if it's a better way, but you can put the cpu and memory charts under the relevant first-level menu sections. Personally, I'm OK with the way it is.
The total absolute stall time is a different metric from what the ratios show. I think we need separate charts for the totals.
Do you mean enable/disable configuration options? Yes, we need them.
I think it is a bug, but I suggest to stick with the workaround for now. |
Sorry, something went wrong.
|
Updated to add a "pressure" section (no dashboard changes yet) and a configuration toggle for every graph. |
Sorry, something went wrong.
|
@ilyam8 Sure, sorry for that. |
Sorry, something went wrong.
There was a problem hiding this comment.
Just a few small fixes and the docs will be ready.
Sorry, something went wrong.
|
I would tend to agree with @ilyam8 on this one. Conceptually, PSI is supposed to be a better replacement for the load average metrics, so I'd suggest at least putting it in the System Overview section like the load average is. In an ideal situation, I'd expect to see the CPU PSI info directly below the main CPU chart (where Load Average is right now), the IO PSI info directly below the main Disk IO charts (though that might be a bit misleading, as the IO tracking is all IO, not just disk IO), and the Memory PSI info directly below the main RAM and Swap charts. |
Sorry, something went wrong.
|
Ok, i read the article And i agree with @Ferroin ideal situation |
Sorry, something went wrong.
I don't see any problems with five more charts since they are useful. If you wish, you can implement them in a different PR. |
Sorry, something went wrong.
Fine, I'll defer that to another PR. |
Sorry, something went wrong.
Just a quick thought, but might it make sense to have the total absolute time charts be optional? Some people may not be interested in them and if there are a lot of cgroups on the system they may want to reduce Netdata's resource usage (RAM and disk space) by turning them off without losing the other charts. Now that I think of it, it may make sense to do similarly for each type of chart (CPU/Memory/IO). |
Sorry, something went wrong.
Currently, all charts are optional and can be turned off individually. |
Sorry, something went wrong.
|
@hexchain please finish with the menu sections so we could merge the PR. |
Sorry, something went wrong.
The charts are now arranged in this way, but I'm kinda unsure about the description texts. |
Sorry, something went wrong.
I think what you've got right now is good actually, it's concise but still conveys the most important information and includes a link to more details, though I'd suggest replacing 'on a given resource' with a reference to the particular resource (CPU/Memory/IO). |
Sorry, something went wrong.
Done. |
Sorry, something went wrong.
There was a problem hiding this comment.
For some reason I can't see my previous requested changes, but at this point the .md and dashboard_info.js content LGTM.
Sorry, something went wrong.
* proc.plugin: add pressure stall information * dashboard_info: add "Pressure" section * proc.plugin: mention PSI collector in doc * dashboard_info: fix grammar in PSI section * proc_pressure: fix wrong line name for "full" metrics * proc_pressure: fix copypasta * proc_pressure: refactor to prepare for cgroup changes * cgroups.plugin: add pressure monitoring * add proc_pressure.h to targets * Makefile.am: fix indentation * cgroups.plugin: remove a useless comment * cgroups.plugin: fix pressure config name * proc.plugin: arrange pressure charts under corresponding sections * dashboard_info: rearrange pressure chart descriptions * dashboard_info: reword PSI descriptions
* proc.plugin: add pressure stall information * dashboard_info: add "Pressure" section * proc.plugin: mention PSI collector in doc * dashboard_info: fix grammar in PSI section * proc_pressure: fix wrong line name for "full" metrics * proc_pressure: fix copypasta * proc_pressure: refactor to prepare for cgroup changes * cgroups.plugin: add pressure monitoring * add proc_pressure.h to targets * Makefile.am: fix indentation * cgroups.plugin: remove a useless comment * cgroups.plugin: fix pressure config name * proc.plugin: arrange pressure charts under corresponding sections * dashboard_info: rearrange pressure chart descriptions * dashboard_info: reword PSI descriptions
| Back | FazBrowse Home | New Git URL |
Summary
Add PSI monitoring to proc.plugin. Fixes #5901.
Component Name
collectors/proc.plugin
Additional Information
This is WIP because:
Things I'd like to make sure before continuing:
- Currently, it resides under "System", and has 5 graphs. Does it deserve its own section?
- Is there a better way to arrange them?
- The "total" fields are not graphed. Do we need them?
- Do we need a switch for each graph (like in proc_loadavg)?
- The procfile_lines returns 2 for /proc/pressure/cpu, which should only have 1 line, for example:
Is this intended or is it a bug? Currently, I'm using lines > 2 to workaround this behavior. What would be a better way to handle this?
Screenshot% python Python 3.7.4 (default, Oct 4 2019, 06:57:26) [GCC 9.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> open('/proc/pressure/cpu', 'rb').read() b'some avg10=3.22 avg60=4.15 avg300=4.07 total=11747246754\n'