Uh oh!
There was an error while loading. Please reload this page.
Conversation
First iteration if the design spec for the logging handler.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| ## Performance Considerations | ||
| <ul> | ||
| <li>While waiting for the logger to finish a trace or span..after a certain amount of time quit the process...<li> | ||
| </ul> |
There was a problem hiding this comment.
Let's add a section on Personally Identifiable Information (PII) considerations. We should be explicit on what we won't log as privacy concerns are a real and growing concern.
There was a problem hiding this comment.
It's also worth mentioning that constantly exporting individual measure can be expensive in terms of network bandwidth and CPU costs, and only aggregated stats should be exported.
Uh oh!
There was an error while loading. Please reload this page.
Second iteration of design spec.
Second iteration of logging handler design spec
| ## Requirements | ||
| ## Requirements | ||
| <ul> |
There was a problem hiding this comment.
Will the logging handler always be present?
How will the LoggingHandler be created?
Do we pass an ILogger and/or OpenCensus Tracer to the logging handler?
What dependencies will the LoggingHandler have?
What requirements will we put on our customers to make use logging handler?
Can you pseudo-code how a customer might instantiate or configure a LoggingHandler?
How do we configure the logging handler?
Uh oh!
There was an error while loading. Please reload this page.
First iteration of the design spec for the logging handler.