Documentation forLoggly

Send Android App Logs to Loggly

You can send your Android logs using our timber-loggly package. It sends logs directly from your application to Loggly using the HTTP/S Event API. For alternatives, please see the Advanced Options section.

Android Logging Setup

1. Add timber-loggly jar

Add a dependency for the timber-loggly jar from the Maven repository or from GitHub. The Maven repository has code snippets to add the dependencies for many common package managers.

For example, if you are using Maven, then add this to the dependencies section of your pom.xml file.


2. Configure timber-loggly

Plant a LogglyTree with your authorization token from Loggly.

import com.github.tony19.timber.loggly.LogglyTree;
import timber.log.Timber;
public class ExampleApp extends Application {
  public void onCreate() {
    final String LOGGLY_TOKEN = "TOKEN";
    Timber.plant(new LogglyTree(LOGGLY_TOKEN));

Use Timber API to log an event via LogglyTree

Timber.i("hello world");


3. Send Test Events

Run your application to send test events to Loggly.

4. Verify Events

Search Loggly for events with the android tag over the past 20 minutes. It may take a few minutes to index the event. If it doesn’t work, see the troubleshooting section below.


Click on one of the logs to show a list of JSON fields (see screenshot below).

Advanced Android Logging Options

Troubleshooting Android Logs

If you don’t see any data show up in the verification step, then check for these common problems.

Check timber-loggly:

  • Wait a few minutes in case indexing needs to catch up
  • See our HTTP Troubleshooting Guide to verify HTTP events are being sent to Loggly.

Still Not Working?

  • Search or post your own questions on Android logging levels, file transport, log messages, and more in the community forum.

When the APM Integrated Experience is enabled, Loggly shares a common navigation and enhanced feature set with the other integrated experiences' products. How you navigate the product and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.