We might be better off not explicitly having a spec define out what is logged
Instead, if we have metaprogramming and at that time want to say Metric A, Metric D, Metric F are sent as logging, it could be passed an an array or something that says which metrics should be logged
I also could see some people wanting to have the option to define it in the spec instead of passing. In that case, there might be a secret / optional field that could be added that allows for defining out in the spec which metrics are going to be logged
Should there be a logging that happens with metrics optionally instead of recording state for each piece of the trajectory?