NewTimber for PythonJun 21st, 2018
We are excited to announce the beta release of Python on Timber. For existing Python users, it’s easy to integrate with your current solution; you only need to add a
handler to your logging module.
If you are already shipping your Python logs to Timber via other means, it is not necessary to switch, though our package automatically collects context to make debugging easier.
Start by educating yourself about logging on Python with a guided tour
If you already are running Python, get up and running today by taking a look at our documentation.
NewTimber Docker Logging Driver v0.1.0Jun 11th, 2018
Our Docker support continues to expand with the release of our Docker logging driver. For existing Docker users, this is an excellent option as no additional processes or containers are required; you only need a few commands to configure the Docker daemon. If you are already shipping your Docker container logs to Timber via our agent or other means there is no need to switch, though our Docker logging driver may end up being easier to manage and use.
To get started, head on over to our docs page.
For more information on Docker logging drivers gohere.
And to view how it all works under the hood take a look at the source code.
NewTimber for KubernetesMay 30th, 2018
With the recent release of v0.8.1 of our Timber Agent, we wanted to highlight its new features:
Kubernetes support has been added to the Timber Agent as of v0.8.0 under the
capture-kube subcommand. Inline with all other Timber offerings, the Kubernetes integration ships logs augmented with contextual information specific to Kubernetes. This information helps identify the log source and includes Pod Name, Container Name, and Deployment Name to list a few. Additional configuration options such as filtering have been added to support a wide range of workflows. More information can be found here and here.
Global State File
In our v0.7.0 release, state moved from being stored in a file per tailed file to a single global file. This change mirrors how other logging agents behave and makes the agent easier to manage in both containerized and virtual machine based environments. By default, the path of the global state file is
/var/lib/timber-agent/statefile.json on Linux and
/var/db/timber-agent/statefile.json on BSD based systems. The location of this file can be configured via the
--statefile cli flag.
Docker is supported and fully functional following our v0.6.2 release. All versions of the Timber Agent Docker container can be found here with the rest of our Docker containers at hub.docker.com/u/timber.io.