From 00151562145df50cc65e9902d52d5fa77f89fe50 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Thu, 9 Jun 2022 06:52:47 +0200 Subject: Merging upstream version 1.35.0. Signed-off-by: Daniel Baumann --- web/gui/dashboard_info.js | 145 +++++++++++++++++++++++++++++++++------------- 1 file changed, 105 insertions(+), 40 deletions(-) (limited to 'web/gui/dashboard_info.js') diff --git a/web/gui/dashboard_info.js b/web/gui/dashboard_info.js index d43577770..35834aaf0 100644 --- a/web/gui/dashboard_info.js +++ b/web/gui/dashboard_info.js @@ -427,7 +427,7 @@ netdataDashboard.menu = { 'web_log': { title: undefined, icon: '', - info: 'Information extracted from a server log file. web_log plugin incrementally parses the server log file to provide, in real-time, a break down of key server performance metrics. For web servers, an extended log file format may optionally be used (for nginx and apache) offering timing information and bandwidth for both requests and responses. web_log plugin may also be configured to provide a break down of requests per URL pattern (check /etc/netdata/python.d/web_log.conf).' + info: 'Information extracted from a server log file. web_log plugin incrementally parses the server log file to provide, in real-time, a break down of key server performance metrics. For web servers, an extended log file format may optionally be used (for nginx and apache) offering timing information and bandwidth for both requests and responses. web_log plugin may also be configured to provide a break down of requests per URL pattern (check /etc/netdata/go.d/web_log.conf).' }, 'squid': { @@ -739,7 +739,7 @@ netdataDashboard.submenu = { }, 'web_log.urls': { - info: 'Number of requests for each URL pattern defined in /etc/netdata/python.d/web_log.conf. This chart counts all requests matching the URL patterns defined, independently of the web server response codes (i.e. both successful and unsuccessful).' + info: 'Number of requests for each URL pattern defined in /etc/netdata/go.d/web_log.conf. This chart counts all requests matching the URL patterns defined, independently of the web server response codes (i.e. both successful and unsuccessful).' }, 'web_log.clients': { @@ -1309,29 +1309,61 @@ netdataDashboard.context = { height: 0.7 }, - 'system.cpu_pressure': { - info: 'Pressure Stall Information ' + - 'identifies and quantifies the disruptions caused by resource contentions. ' + - 'The "some" line indicates the share of time in which at least some tasks are stalled on CPU. ' + - 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' + 'system.cpu_some_pressure': { + info: 'CPU Pressure Stall Information. '+ + 'Some indicates the share of time in which at least some tasks are stalled on CPU. ' + + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'system.cpu_some_pressure_stall_time': { + info: 'The amount of time some processes have been waiting for CPU time.' + }, + 'system.cpu_full_pressure': { + info: 'CPU Pressure Stall Information. ' + + 'Full indicates the share of time in which all non-idle tasks are stalled on CPU resource simultaneously. ' + + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'system.cpu_full_pressure_stall_time': { + info: 'The amount of time all non-idle processes have been stalled due to CPU congestion.' }, 'system.memory_some_pressure': { - info: 'Pressure Stall Information ' + - 'identifies and quantifies the disruptions caused by resource contentions. ' + - 'The "some" line indicates the share of time in which at least some tasks are stalled on memory. ' + - 'The "full" line indicates the share of time in which all non-idle tasks are stalled on memory simultaneously. ' + - 'In this state actual CPU cycles are going to waste, and a workload that spends extended time in this state is considered to be thrashing. ' + - 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' + info: 'Memory Pressure Stall Information. '+ + 'Some indicates the share of time in which at least some tasks are stalled on memory. ' + + 'In this state the CPU is still doing productive work. '+ + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'system.memory_some_pressure_stall_time': { + info: 'The amount of time some processes have been waiting due to memory congestion.' + }, + 'system.memory_full_pressure': { + info: 'Memory Pressure Stall Information. ' + + 'Full indicates the share of time in which all non-idle tasks are stalled on memory resource simultaneously. ' + + 'In this state actual CPU cycles are going to waste, and a workload that spends extended time in this state is considered to be thrashing. '+ + 'This has severe impact on performance. '+ + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'system.memory_full_pressure_stall_time': { + info: 'The amount of time all non-idle processes have been stalled due to memory congestion.' }, 'system.io_some_pressure': { - info: 'Pressure Stall Information ' + - 'identifies and quantifies the disruptions caused by resource contentions. ' + - 'The "some" line indicates the share of time in which at least some tasks are stalled on I/O. ' + - 'The "full" line indicates the share of time in which all non-idle tasks are stalled on I/O simultaneously. ' + - 'In this state actual CPU cycles are going to waste, and a workload that spends extended time in this state is considered to be thrashing. ' + - 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' + info: 'I/O Pressure Stall Information. '+ + 'Some indicates the share of time in which at least some tasks are stalled on I/O. ' + + 'In this state the CPU is still doing productive work. '+ + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'system.io_some_pressure_stall_time': { + info: 'The amount of time some processes have been waiting due to I/O congestion.' + }, + 'system.io_full_pressure': { + info: 'I/O Pressure Stall Information. ' + + 'Full line indicates the share of time in which all non-idle tasks are stalled on I/O resource simultaneously. ' + + 'In this state actual CPU cycles are going to waste, and a workload that spends extended time in this state is considered to be thrashing. '+ + 'This has severe impact on performance. '+ + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'system.io_full_pressure_stall_time': { + info: 'The amount of time all non-idle processes have been stalled due to I/O congestion.' }, 'system.io': { @@ -4026,14 +4058,33 @@ netdataDashboard.context = { 'When an application has used its allotted CPU quota for a given period, it gets throttled until the next period.' }, + 'cgroup.cpu_shares': { + info: '

The weight of each group living in the same hierarchy, that translates into the amount of CPU it is expected to get. '+ + 'The percentage of CPU assigned to the cgroup is the value of shares divided by the sum of all shares in all cgroups in the same level.

'+ + '

For example, tasks in two cgroups that have cpu.shares set to 100 will receive equal CPU time, '+ + 'but tasks in a cgroup that has cpu.shares set to 200 receive twice the CPU time of tasks in a cgroup where cpu.shares is set to 100.

' + }, + 'cgroup.cpu_per_core': { info: 'Total CPU utilization per core within the system-wide CPU resources.' }, - 'cgroup.cpu_pressure': { + 'cgroup.cpu_some_pressure': { info: 'CPU Pressure Stall Information. '+ - 'Some indicates the share of time in which at least some tasks are stalled on CPU. '+ - 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' + 'Some indicates the share of time in which at least some tasks are stalled on CPU. ' + + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'cgroup.cpu_some_pressure_stall_time': { + info: 'The amount of time some processes have been waiting for CPU time.' + }, + + 'cgroup.cpu_full_pressure': { + info: 'CPU Pressure Stall Information. ' + + 'Full indicates the share of time in which all non-idle tasks are stalled on CPU resource simultaneously. ' + + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'cgroup.cpu_full_pressure_stall_time': { + info: 'The amount of time all non-idle processes have been stalled due to CPU congestion.' }, 'cgroup.mem_utilization': { @@ -4119,18 +4170,25 @@ netdataDashboard.context = { 'Swap - major page faults.

' }, - 'cgroup.memory_pressure': { + 'cgroup.memory_some_pressure': { info: 'Memory Pressure Stall Information. '+ - 'Some indicates the share of time in which at least some tasks are stalled on memory. '+ - 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' + 'Some indicates the share of time in which at least some tasks are stalled on memory. ' + + 'In this state the CPU is still doing productive work. '+ + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'cgroup.memory_some_pressure_stall_time': { + info: 'The amount of time some processes have been waiting due to memory congestion.' }, 'cgroup.memory_full_pressure': { - info: 'Memory Pressure Stall Information. '+ - 'Full indicates the share of time in which all non-idle tasks are stalled on memory simultaneously. '+ - 'In this state actual CPU cycles are going to waste, '+ - 'and a workload that spends extended time in this state is considered to be thrashing. '+ - 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' + info: 'Memory Pressure Stall Information. ' + + 'Full indicates the share of time in which all non-idle tasks are stalled on memory resource simultaneously. ' + + 'In this state actual CPU cycles are going to waste, and a workload that spends extended time in this state is considered to be thrashing. '+ + 'This has severe impact on performance. '+ + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'cgroup.memory_full_pressure_stall_time': { + info: 'The amount of time all non-idle processes have been stalled due to memory congestion.' }, 'cgroup.io': { @@ -4190,18 +4248,25 @@ netdataDashboard.context = { info: 'The number of I/O operations performed on specific devices as seen by the throttling policy.' }, - 'cgroup.io_pressure': { + 'cgroup.io_some_pressure': { info: 'I/O Pressure Stall Information. '+ - 'Some indicates the share of time in which at least some tasks are stalled on I/O. '+ - 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' + 'Some indicates the share of time in which at least some tasks are stalled on I/O. ' + + 'In this state the CPU is still doing productive work. '+ + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'cgroup.io_some_pressure_stall_time': { + info: 'The amount of time some processes have been waiting due to I/O congestion.' }, 'cgroup.io_full_pressure': { - info: 'I/O Pressure Stall Information. '+ - 'Full indicates the share of time in which all non-idle tasks are stalled on I/O simultaneously. '+ - 'In this state actual CPU cycles are going to waste, '+ - 'and a workload that spends extended time in this state is considered to be thrashing. '+ - 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' + info: 'I/O Pressure Stall Information. ' + + 'Full line indicates the share of time in which all non-idle tasks are stalled on I/O resource simultaneously. ' + + 'In this state actual CPU cycles are going to waste, and a workload that spends extended time in this state is considered to be thrashing. '+ + 'This has severe impact on performance. '+ + 'The ratios are tracked as recent trends over 10-, 60-, and 300-second windows.' + }, + 'cgroup.io_full_pressure_stall_time': { + info: 'The amount of time all non-idle processes have been stalled due to I/O congestion.' }, 'cgroup.swap_read': { @@ -4931,7 +4996,7 @@ netdataDashboard.context = { }, 'web_log.clients_all': { - info: 'Unique client IPs accessing the web server since the last restart of netdata. This plugin keeps in memory all the unique IPs that have accessed the web server. On very busy web servers (several millions of unique IPs) you may want to disable this chart (check /etc/netdata/python.d/web_log.conf).' + info: 'Unique client IPs accessing the web server since the last restart of netdata. This plugin keeps in memory all the unique IPs that have accessed the web server. On very busy web servers (several millions of unique IPs) you may want to disable this chart (check /etc/netdata/go.d/web_log.conf).' }, // ------------------------------------------------------------------------ @@ -5062,7 +5127,7 @@ netdataDashboard.context = { }, 'web_log.squid_clients_all': { - info: 'Unique client IPs accessing squid since the last restart of netdata. This plugin keeps in memory all the unique IPs that have accessed the server. On very busy squid servers (several millions of unique IPs) you may want to disable this chart (check /etc/netdata/python.d/web_log.conf).' + info: 'Unique client IPs accessing squid since the last restart of netdata. This plugin keeps in memory all the unique IPs that have accessed the server. On very busy squid servers (several millions of unique IPs) you may want to disable this chart (check /etc/netdata/go.d/web_log.conf).' }, 'web_log.squid_transport_methods': { -- cgit v1.2.3