Ben Johnson

For various platforms we recommend direct platform integration. The installer should leverage the API to understand which delivery method is recommended. This avoids platform configuration from getting out of sync.

Adding network request details to the logs provides insight into service interaction. If this is performed within a http request we should carry over the `request_id` so that this can...

This ensures Timber middlewares work outside of a Rails environment.

Ability to turn off logging user names for HIPPA compliance

1

We need a setting for this. I'm wondering if there is any real value in capturing the name if we get the email and id.

We're going to start building in memory and cpu usage into the interface. This will also be included in the new dashboards feature in the future. Users using the libraries...

Just like our agent, we should attempt to capture EC2 metadata if the ruby application is on an EC2 server.

Flush log data before process exit

2

In short lived processes Timber will not deliver log data because it maintains a buffer and flushes on an interval. Timber should flush the buffer before the process exits.

Currently the `controller_call` event has a `params_json` field that represents all parameters encoded in JSON. Because Timber manages application schema's on the fly, capturing these as individual fields can quickly...

This would be helpful for debugging if it could be run from the server: ``` bundle exec timber test-the-pipes ```

This is captured as metadata, so we do not need to log it in the message as well. Example: ``` Processing by Spree::OrdersController#populate as HTML Aug 30 08:25:33pm app[web.1] info:...