languages / elixir / troubleshooting

Elixir Troubleshooting

If you're having trouble don't hesitate to contact us! We're passionate about helping our customers and providing good user experiences.

This is fine

If you are here, it's likely you're having trouble sending logs from your application to Timber. Not to worry! This document will help you identify the root cause. To use your time as efficiently as possible here are the steps you should take:

1. Rule out Timber service issues by testing delivery

The very first thing you should do is rule out that Timber is not the cause by sending a simple test log to your Timber application. First, try it locally. If that works, try it on your application's server. The latter being the most important.

curl -X POST \
  -H 'authorization: Basic base64_encode({{my-timber-api-key}})' \
  -H 'content-type: text/plain' \
  -d 'Test log line to test delivery'

Be sure to base 64 encode your API key. Here's an example with Ruby.


Then paste in:

require "base64"

On average log lines will appear within 5 seconds of delivery but in some cases can take up to 20 seconds depending on network latency, etc.

2. Enable debug logging within the Timber library

Timber comes packaged with debugging options, this will give you access to the internal debug logs that the Timber library produces. Enabling them is easy:

# config/config.exs
config :timber,
  debug_io_device: :stdio

What to do with the logs?

Look for the term error. Specifically a log that looks like this:

HTTP request ... received response ...

If you do not see any errors, but instead you see:

HTTP request ... received response 200

Then your application is delivering logs appropriately.

What if none of this resolved my issue?

Contact us. We're passionate about helping customers, we'll do our best to find the root cause.


Chat with us, just click the talk button in the bottom right of this page.

Chat with us
Sign Up

Log better and solve problems faster, today. Install in under a minute.

Sign Up