Adding objectTrace logger to output configurable fields to a new log file from PickUpPlace

[arp-0984]

No description provided.

[cfkoehler]

I am good with this once the one comment I left is resolved.
I imported this into our other project and messed with the overrides and such and all worked as I would expect

[arp-0984]

The Super-Linter job keeps failing: "DOCKERFILE_HADOLINT_LINTER_RULES rules file (/action/lib/.automation/../../contrib/docker/.hadolint.yaml) doesn't exist. Terminating..."

This may be an issue with the job itself - I saw it was updated recently. I'm not sure why my 1-line change would have caused this issue if it passed before.

[drivenflywheel]

Would like to see the implementation better encapsulated so Places can integrate with less coupling.

[drivenflywheel]

If we think the events we emit we may need to have environment-specific fields, we should consider using the Service Provider pattern that leverages the support we have in the emissary.spi package. The ObjectTracing class could leverage an environment-specific "service" that's responsible for constructing the event-specific/stage-specific entries. The SPILoader bootstrapping would allow us to select the specific service implementation to use at runtime, but the ObjectTracing class would internally just be coded against the service interface. If that's too much for this initial PR, maybe we can address it in a follow-up PR.

[arp-0984]

If we think the events we emit we may need to have environment-specific fields, we should consider using the Service Provider pattern that leverages the support we have in the emissary.spi package. The ObjectTracing class could leverage an environment-specific "service" that's responsible for constructing the event-specific/stage-specific entries. The SPILoader bootstrapping would allow us to select the specific service implementation to use at runtime, but the ObjectTracing class would internally just be coded against the service interface. If that's too much for this initial PR, maybe we can address it in a follow-up PR.

I'm investigating this, not sure if it is best to do in this PR or a follow-up PR.

[drivenflywheel]

I'm investigating this, not sure if it is best to do in this PR or a follow-up PR.
Follow-up PR is probably the right choice. I just wanted to capture the potential approach.