A customer reports a Linux production server is randomly suffering degraded performance. The administrator verifies that the package is installed and enabled on the server. sysstat Which of the…

While collecting historical data is good, `sysstat` already does this, so creating a new job to duplicate this function is redundant and less efficient than using existing data.

A ping only checks network connectivity and latency; it does not provide detailed system performance metrics like CPU, memory, or disk I/O that `sysstat` captures.

The `sysstat` package includes utilities like `sar` (System Activity Report) which collects and reports system activity information, and `sadf` which is used to display `sar` data in various formats. Analyzing the historical data collected by `sysstat` using `sar` or `sadf` provides insights into past performance bottlenecks without needing to proactively capture new data.

Running `top` in a screen session overnight provides real-time snapshot data but does not easily allow for historical analysis of trends or specific events that might have occurred hours ago, unlike `sysstat`'s persistent logging.