v0.0.11

Adds several convenience functions on the builders to reduce code noise, changes default level of log to debug.

What's Changed

• Adjust log level, convenience functions by @ChristopherDavenport in #13

Full Changelog: v0.0.10...v0.0.11

v0.0.10

• Allow dynamic removal of context keys
• Allow configuration of the request and response encoders
• Move client logging so that it happen independent of draining of the response body by the user.

What's Changed

• With Dynamic removedContextKeys by @ChristopherDavenport in #10
• Configurable Body Encoders by @ChristopherDavenport in #11
• Client Log When Response Not Drained by @ChristopherDavenport in #12

Full Changelog: v0.0.9...v0.0.10

v0.0.9

The User and Ident protocols are not implemented, as a result there are some very defined fields that can be used to make this logging more beneficial. This is included to make folks have tools to improve the CommonLog should they leverage it themselves.

What's Changed

• Allow abstraction of user and ident protocols by @ChristopherDavenport in #9

Full Changelog: v0.0.8...v0.0.9

v0.0.8

Several Headers Identified that are safe and common enough to be included.

What's Changed

• Add additional allowed headers by @ChristopherDavenport in #8

Full Changelog: v0.0.7...v0.0.8

v0.0.7

• Use Common Log for Both Client and Server (For Client we prefix with HttpClient so its clear its different, as well as use base rather than origin form)
• Expose Common Log, as well as add functionality for it to serve CombinedLog format.
• Switch the default logLevel function. Rather than everything at info have it automatically adjust the log level based on status (4xx-Warn, 5xx-Error), as well as Cancels and Errors of the effect
• Use additionalContext function in ClientMiddleware
• Expose a quietLogLevel default function that does not log on what were previously info logs.

What's Changed

• Client and logs by @ChristopherDavenport in #7

Full Changelog: v0.0.6...v0.0.7

v0.0.6

Rather than Request/Response => Map[String, String] instead prefer providing the entire context for addtional attributes (Request, Outcome[Option, Throwable, Response]) => Map[String, String]

Rather than removing headers keys not in the set, include them but redact the values.

What's Changed

• Give outcome information to additional context by @ChristopherDavenport in #6

Full Changelog: v0.0.5...v0.0.6

v0.0.5

This release tries to standardize name access so that there are less floating contexts.

What's Changed

• Centralize Context Namespacing by @ChristopherDavenport in #5

Full Changelog: v0.0.4...v0.0.5

v0.0.4

SelfAwareStructuredLogger is useful but for a capability we aren't using that get in the way of how many people build their context loggers. So dropping constraint to StructuredLogger should make this more easily accesible.

What's Changed

• Only Require Context Logging since we dont use awareness by @ChristopherDavenport in #4

Full Changelog: v0.0.3...v0.0.4

v0.0.3

Better Context!

• Adds contextlog.kind which differentiates server/client, especially useful if you leverage the same log function.
• Separate the headers and body times into duration_ms(headers) and duration_body_ms(body), the latter will only be present if you are logging the body as otherwise you are only tied into the request app cycle.
• Adds http.access_time in epoch millis, standardized on access time so all log functions use the same relative time.

What's Changed

• Add contextlog.kind, seperate body and header durations by @ChristopherDavenport in #1
• Time should be access time, adjust inputs by @ChristopherDavenport in #2
• Reduce Request Context Duplication by @ChristopherDavenport in #3

New Contributors

• @ChristopherDavenport made their first contribution in #1

Full Changelog: v0.0.2...v0.0.3

v0.0.2

Expose HttpStructuredContext which will allow folks to expose their own increased set of allowed headers.