.@chris I’ve parsed a lot of things like this with awk / nawk / gawk.

Put multiple lines in an awk script (.awk) that match patterns and set variables.

Then after you e matched the last line, do what you want with the variables. E.g.

($1 == “Running”){
runningMode=$4
state=$7}

($1 == “Power”){
powerManagementMode=$5
print state, powerManagementMode, runningMode

runningMode=“”
state=“”
powerManagementMode=“”
}

The idea is match lines that should have known value(s) in specific field(s) and use set variables to the proper values on the matched line.

Once you see the last line (in a set) then use the variables and set the variables to default / control values.

I’ve had great success with this as a #sysadmin

This is just for an idea, all typose are my cats fault. Negative warranty provided. 😉

I’d like to directly make use of the source and create an initial, human readable template by marking up dynamic parts in an effective way.
There are nice approaches to #templates for formatting #output. I’d like to find something similar for #input without reinventing a crutch and calling it a wheel.
(Yes, in an ideal parallel universe every source has a switch to output structured data.)

I’ll have to have a thorough look into existing ways of templating output, first. (2/2)