You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
use per-disk/per-network-interface metrics instead of aggregated host metrics (that are already computed by the module), meaning that in the Dashboard [Metricbeat System] Host overview ECS we are not getting a whole host view, but rather the disk/network interface with the most reads/writes. Further, since we are computing the derivative of a max, we can potentially compare different disks/network interfaces in different intervals potentially yielding to misleading results.
The suggestion of this issue is to use the aggregated fields in the dashboards. In the following table I list the current fields in use and the proposed fields:
Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!
Describe the enhancement:
As of now the visualizations:
Disk IO (Bytes) [Metricbeat System] ECS
Network Traffic (Bytes) [Metricbeat System] ECS
Network Traffic (Packets) [Metricbeat System] ECS
use per-disk/per-network-interface metrics instead of aggregated host metrics (that are already computed by the module), meaning that in the Dashboard
[Metricbeat System] Host overview ECS
we are not getting a whole host view, but rather the disk/network interface with the most reads/writes. Further, since we are computing the derivative of a max, we can potentially compare different disks/network interfaces in different intervals potentially yielding to misleading results.The suggestion of this issue is to use the aggregated fields in the dashboards. In the following table I list the current fields in use and the proposed fields:
system.diskio.read.bytes
system.diskio.write.bytes
host.disk.read.bytes
host.disk.write.bytes
system.network.in.bytes
system.network.out.bytes
host.network.ingress.bytes
host.network.egress.bytes
system.network.in.packets
system.network.out.packets
host.network.ingress.packets
host.network.egress.packets
Describe a specific use case for the enhancement or feature:
The use-case for this enhancement is to have a "whole" host view instead of the disk/network-interface with the most read/writes.
Related Issue
elastic/integrations#6565
The text was updated successfully, but these errors were encountered: