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
- Rename CPU count -> Cores in fleet table
- Change filesystem space available TS graph to bytes (same as linux)
- Add networkErrorsAndDroppedPerSec(use in overview) and networkErrorsAndDroppedPerSecTopK(use in fleet dashboard) panels for errs and drops together
- Add fleet table footer (same as linux)
Network errors refer to issues that occur during the transmission of data across a network.
382
+
383
+
These errors can result from various factors, including physical issues, jitter, collisions, noise and interference.
384
+
385
+
Monitoring network errors is essential for diagnosing and resolving issues, as they can indicate problems with network hardware or environmental factors affecting network quality.
386
+
387
+
**Dropped packets**:
388
+
389
+
Dropped packets occur when data packets traveling through a network are intentionally discarded or lost due to congestion, resource limitations, or network configuration issues.
390
+
391
+
Common causes include network congestion, buffer overflows, QoS settings, and network errors, as corrupted or incomplete packets may be discarded by receiving devices.
392
+
393
+
Dropped packets can impact network performance and lead to issues such as degraded voice or video quality in real-time applications.
0 commit comments