vmstat
--vmstatv1.4.0Converts `vmstat` command output to JSON
Linuxcommand
$ vmstat | jc-rs --vmstatA real pair
From the reference corpus (centos-7.7/vmstat.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.
vmstatcentos-7.7
procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 2 0 0 2794468 2108 741208 0 0 1 3 29 57 0 0 99 0 0
expected outputjson
Use the Left and Right arrow keys to highlight the matching value in the input.
[ { "runnable_procs": 2, "uninterruptible_sleeping_procs": 0, "virtual_mem_used": 0, "free_mem": 2794468, "buffer_mem": 2108, "cache_mem": 741208, "inactive_mem": null, "active_mem": null, "swap_in": 0, "swap_out": 0, "blocks_in": 1, "blocks_out": 3, "interrupts": 29, "context_switches": 57, "user_time": 0, "system_time": 0, "idle_time": 99, "io_wait_time": 0, "stolen_time": 0, "timestamp": null, "timezone": null } ]
Fixture coverage
9/9oracle-valid pairs match under the published structural JSON comparison
Magic syntax
jc-rs vmstatjc-rs runs the command itself and parses what it prints. Recognised for: `vmstat`Source: crates/jc-rs-parsers/src/system/vmstat.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare