Monitor (host) memory / disk space / load usage during runs

[Julian]

We've had woes in GH Actions with disk space filling up.

But it strikes me as anyhow interesting to collect information about memory/disk/CPU usage on the host machine during Bowtie runs. This might be useful for detecting implementation issues (you ate all my disk space), but also perhaps for introspection reasons.

If/when we do this, we should likely instrument GITHUB_STEP_SUMMARY with some run info.

#35 is slightly related from an introspection standpoint.

#19 is related inasmuch as we should be careful what "host" means -- though this is true even for Docker use cases -- as the machine where containers are running might be different from the one Bowtie is running on.

[OptimumCode]

Hi, @Julian. I found this action on GitHub marketplace. Maybe it can be used to collect the required telemetry during the workflow run

[Julian]

Cool! Could indeed be a nice stopgap, thanks for finding it!