Known issue (1.6): When the Agent PacketDrop feature is enabled, and sampling is configured greater than 1, reported dropped bytes and packet ignore the sampling configuration. While this is done on purpose to not miss any drop, a side effect is that the reported proportion of drops versus non-drops becomes biased. At very high sampling rate, such as 1:1000, it's likely that almost all the traffic appears to be dropped, when looked from the console plugin. But this is only a bias. Fix (1.6.1): When the eBPF agent `PacketDrop` feature is enabled, and sampling is configured to a value greater than `1`, reported dropped bytes and dropped packets was ignoring the sampling configuration. While this was done on purpose to not miss any drops, a side effect was that the reported proportion of drops versus non-drops became biased. For example, at a very high sampling rate, such as `1:1000`, it was likely that almost all the traffic appears to be dropped when observed from the console plugin. The new behaviour is to honour the sampling configuration with dropped bytes and packets.