Ben Johnson
Ben Johnson
Timber's various configuration parameters do not consistently support pulling values via a `{:system, "VAR_NAME"}` tuple. For example, [`Timber.Config.api_key/0`](https://github.com/timberio/timber-elixir/blob/20ec4a520fe94f15b5812337cfc8a54528aff69e/lib/timber/config.ex#L17) does, yet [`Timber.Config.http_url/0`](https://github.com/timberio/timber-elixir/blob/20ec4a520fe94f15b5812337cfc8a54528aff69e/lib/timber/config.ex#L85) does not. This makes it challenging to change all...
Assuming the byte_size is readily available, we should map this to the `content_length` field for all HTTP request and response events. We should also include this in the actual log...
``` mix timber.test-the-pipes ``` Would run various checks to ensure logs are being delivered from the source machine.
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...
We should include a simple mix task that "tests the pipes" to ensure everything is working correct.
Originally I looked into how to do this and couldn't figure it out because there is no way to get the previously set configuration values. If we can't do this,...
We had a user request this and we support it. We need to provide options for this.
We added a new `time_ms` attribute. It'd be great if we could add a sample feature to this, where they could sample a timing every 1 second, for example.
The TOC on [this page](https://docs.timber.io/platforms/syslog/install/rsyslog/) floats over the content. It appears to be due to the long breadcrumbs.
### A note for the community * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request...