The Metric System Overview dashboard has two main issue in the configuration of the Top Hosts by CPU lens table.
The first issue is the configured reducedTimeRange property of the of the two CPU and Memory columns. This property if fixed at 10s meaning the last value picked for these two fields is picked only in the last 10s of the current time window. Depending on that time window there is always the possibility that this bucket is empty reporting missing data in the columns.
See here for configuration of the two columns
|
"5a603425-af67-4d0f-a69c-efe9cb9c398a": { |
|
"customLabel": true, |
|
"dataType": "number", |
|
"filter": { |
|
"language": "kuery", |
|
"query": "\"system.memory.actual.used.pct\": *" |
|
}, |
|
"isBucketed": false, |
|
"label": "Memory usage", |
|
"operationType": "last_value", |
|
"params": { |
|
"format": { |
|
"id": "percent" |
|
}, |
|
"sortField": "@timestamp" |
|
}, |
|
"reducedTimeRange": "10s", |
|
"scale": "ratio", |
|
"sourceField": "system.memory.actual.used.pct" |
|
}, |
|
"8751e403-1391-434e-9dd2-4b45ef833305": { |
|
"customLabel": true, |
|
"dataType": "number", |
|
"filter": { |
|
"language": "kuery", |
|
"query": "\"system.process.cpu.total.norm.pct\": *" |
|
}, |
|
"isBucketed": false, |
|
"label": "CPU usage", |
|
"operationType": "last_value", |
|
"params": { |
|
"format": { |
|
"id": "percent" |
|
}, |
|
"sortField": "@timestamp" |
|
}, |
|
"reducedTimeRange": "10s", |
|
"scale": "ratio", |
|
"sourceField": "system.process.cpu.total.norm.pct" |
|
} |
The second issue is related to the color by value configuration: the configuration uses the relative configuration (currently wrongly called Percent elastic/kibana#173786) that causes the color to be applied to the current data domain: the 100% is applied to the current data max, and the 0% is the current data min. This results in coloring for example a value of 2% red if that is the top value available in that column.
|
{ |
|
"colorMode": "cell", |
|
"columnId": "8751e403-1391-434e-9dd2-4b45ef833305", |
|
"palette": { |
|
"name": "custom", |
|
"params": { |
|
"colorStops": [ |
|
{ |
|
"color": "#209280", |
|
"stop": 0 |
|
}, |
|
{ |
|
"color": "#d6bf57", |
|
"stop": 70 |
|
}, |
|
{ |
|
"color": "#cc5642", |
|
"stop": 85 |
|
} |
|
], |
|
"continuity": "above", |
|
"name": "custom", |
|
"rangeMax": null, |
|
"rangeMin": 0, |
|
"reverse": false, |
|
"steps": 5, |
|
"stops": [ |
|
{ |
|
"color": "#209280", |
|
"stop": 70 |
|
}, |
|
{ |
|
"color": "#d6bf57", |
|
"stop": 85 |
|
}, |
|
{ |
|
"color": "#cc5642", |
|
"stop": 100 |
|
} |
|
] |
|
}, |
|
"type": "palette" |
|
} |
|
}, |
|
{ |
|
"colorMode": "cell", |
|
"columnId": "5a603425-af67-4d0f-a69c-efe9cb9c398a", |
|
"isTransposed": false, |
|
"palette": { |
|
"name": "custom", |
|
"params": { |
|
"colorStops": [ |
|
{ |
|
"color": "#209280", |
|
"stop": 0 |
|
}, |
|
{ |
|
"color": "#d6bf57", |
|
"stop": 70 |
|
}, |
|
{ |
|
"color": "#cc5642", |
|
"stop": 85 |
|
} |
|
], |
|
"continuity": "above", |
|
"name": "custom", |
|
"rangeMax": null, |
|
"rangeMin": 0, |
|
"reverse": false, |
|
"steps": 5, |
|
"stops": [ |
|
{ |
|
"color": "#209280", |
|
"stop": 70 |
|
}, |
|
{ |
|
"color": "#d6bf57", |
|
"stop": 85 |
|
}, |
|
{ |
|
"color": "#cc5642", |
|
"stop": 100 |
|
} |
|
] |
|
}, |
|
"type": "palette" |
|
} |
|
} |
The table should instead be reconfigured to use
Number value type and use ratios to apply correctly colors to percent values (this is also confusing from the Lens side and needs to be fixed
elastic/kibana#179922)
I think these issues can be tracked back to this PR #6743
Probably the conversion between TSVB and Lens was not fully verified and something slipped through
The Metric System Overview dashboard has two main issue in the configuration of the
Top Hosts by CPUlens table.The first issue is the configured
reducedTimeRangeproperty of the of the two CPU and Memory columns. This property if fixed at10smeaning thelast valuepicked for these two fields is picked only in the last 10s of the current time window. Depending on that time window there is always the possibility that this bucket is empty reporting missing data in the columns.See here for configuration of the two columns
integrations/packages/system/kibana/dashboard/system-Metrics-system-overview.json
Lines 429 to 468 in 2060587
The second issue is related to the color by value configuration: the configuration uses the
relativeconfiguration (currently wrongly calledPercentelastic/kibana#173786) that causes the color to be applied to the current data domain: the 100% is applied to the current data max, and the 0% is the current data min. This results in coloring for example a value of 2% red if that is the top value available in that column.integrations/packages/system/kibana/dashboard/system-Metrics-system-overview.json
Lines 550 to 638 in 2060587
The table should instead be reconfigured to use
Numbervalue type and use ratios to apply correctly colors to percent values (this is also confusing from the Lens side and needs to be fixed elastic/kibana#179922)I think these issues can be tracked back to this PR #6743
Probably the conversion between TSVB and Lens was not fully verified and something slipped through