David Antaramian

Rationale for choices

8

One of the things I discussed with Christoper earlier via Slack is that I didn't agree with some of the positions taken in the style guide. That's not a criticism...

[Request that results in 5XX responses are retried up to 3 times](https://github.com/timberio/library-specification/blob/master/SPECIFICATION.MD#3331-batching-and-buffering-log-data)

[Retries utilize an exponential backoff with jitter](https://github.com/timberio/library-specification/blob/master/SPECIFICATION.MD#3331-batching-and-buffering-log-data)

logfmt should not print `@metadata` separator

1

@binarylogic Deferring to you on this, but I don't think it should. Example: 

Testing mechanism needs to use CaptureLog

3

We can use https://hexdocs.pm/ex_unit/ExUnit.CaptureLog.html#content to capture logs, but for some reason it's outputting ANSI data in the log data when it shouldn't be. Once that's resolved, this should resolve a...

See #231 A user should be able to configure `Timber.Integrations.PhoenixInstrumenter` so that it does _not_ log channel events. This should be part of application-level configuration.

@pmarreck provided a code snippet for adding the user context based on a Coherence session. We should add this to documentation (with appropriate credit). This can probably go into the...

Add a syslog transport

4

See https://github.com/Vagabond/erlang-syslog/blob/master/src/syslog.erl for example of how this has been done before

Absinthe Middleware

1

We've had some people ask about Absinthe middleware that sets context information during a GraphQL query. We'll need to build an app to test this on, though.

Use application specific configuration keys

6

I was responding to a question someone had about this package, and I noticed that you're using the `:logger` application configuration to hold configuration specific to this package. You should...