This PR adds a small document describing at a high level how the stack's logging structure is laid out, and specifies the common event properties that are shared across the two main log files (in enough detail to be able to identify if a stack has any issues, and if so what products are impacted/why/etc).
Part of this included standardising some property names (there were various inconsistencies across logged events).
I think this finally addresses #186 - given the outcome of this PR is a definitive way to determine the status of specific products (which means we have enough logging context to do it!)
(for the curious, AU spelling was accepted over US spelling in discussions w/ InSAR team & project owner Matt - as AU is the country of origin of this software)
This PR adds a small document describing at a high level how the stack's logging structure is laid out, and specifies the common event properties that are shared across the two main log files (in enough detail to be able to identify if a stack has any issues, and if so what products are impacted/why/etc).
Part of this included standardising some property names (there were various inconsistencies across logged events).
I think this finally addresses #186 - given the outcome of this PR is a definitive way to determine the status of specific products (which means we have enough logging context to do it!)
(for the curious, AU spelling was accepted over US spelling in discussions w/ InSAR team & project owner Matt - as AU is the country of origin of this software)