As a carbon aware developer, I can access consistent telemetry libraries and utilities so that I can plumb through telemetry signals throughout the project.
Design Goals
minimal maintenance of tracing when new features are added
starting a single trace per request/command on "entry"
only start additional traces on network "exit" (EG - network request boundaries like EM API calls, etc)
Stretch Goal
Connecting "entry" traces to potential parent traces that have already started in another service.
User Story
As a carbon aware developer, I can access consistent telemetry libraries and utilities so that I can plumb through telemetry signals throughout the project.
Design Goals
Stretch Goal
Acceptance Criteria