Missing Timber.v? about timber

[JakeWharton]

I didn't think the distinction was useful. Do you use all 5 levels?

[imminent]

I primarily use v d and e, I guess I can just remap my logs, just curious.
I find it hard to decide the distinctions between log levels sometimes
anyways

On Wednesday, November 20, 2013, Jake Wharton wrote:

I didn't think the distinction was useful. Do you use all 5 levels?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-28921939
.

Dandré Allison [phone]
KeepandShare.com http://www.keepandshare.com

          Schedule & Share. Simply. Securely.

[JakeWharton]

That's why I axed it down to four. Error: really bad exception, warning: exception but not that bad, info: app flow and status messages, debug: noisy debug-only info.

In my real apps I use the following as the only planted Tree:

package com.squareup.wallet.data;

import com.crashlytics.android.Crashlytics;
import timber.log.Timber;

/**
 * A logging implementation which reports 'info', 'warning', and 'error' logs to Crashlytics.
 */
public class CrashlyticsTree extends Timber.HollowTree {
  @Override public void i(String message, Object... args) {
    logMessage(message, args);
  }

  @Override public void i(Throwable t, String message, Object... args) {
    logMessage(message, args);
    // NOTE: We are explicitly not sending the exception to Crashlytics here.
  }

  @Override public void w(String message, Object... args) {
    logMessage("WARN: " + message, args);
  }

  @Override public void w(Throwable t, String message, Object... args) {
    logMessage("WARN: " + message, args);
    // NOTE: We are explicitly not sending the exception to Crashlytics here.
  }

  @Override public void e(String message, Object... args) {
    logMessage("ERROR: " + message, args);
  }

  @Override public void e(Throwable t, String message, Object... args) {
    logMessage("ERROR: " + message, args);
    Crashlytics.logException(t);
  }

  private void logMessage(String message, Object... args) {
    Crashlytics.log(String.format(message, args));
  }
}

[imminent]

Got it, nice example.
On Nov 20, 2013 12:42 PM, "Jake Wharton" [email protected] wrote:

That's why I axed it down to four. Error: really bad exception, warning:
exception but not that bad, info: app flow and status messages, debug:
noisy debug-only info.

In my real apps I use the following as the only planted Tree:

package com.squareup.wallet.data;
import com.crashlytics.android.Crashlytics;import timber.log.Timber;
/** * A logging implementation which reports 'info', 'warning', and 'error' logs to Crashlytics. */public class CrashlyticsTree extends Timber.HollowTree {
@OverRide public void i(String message, Object... args) {
logMessage(message, args);
}

@OverRide public void i(Throwable t, String message, Object... args) {
logMessage(message, args);
// NOTE: We are explicitly not sending the exception to Crashlytics here.
}

@OverRide public void w(String message, Object... args) {
logMessage("WARN: " + message, args);
}

@OverRide public void w(Throwable t, String message, Object... args) {
logMessage("WARN: " + message, args);
// NOTE: We are explicitly not sending the exception to Crashlytics here.
}

@OverRide public void e(String message, Object... args) {
logMessage("ERROR: " + message, args);
}

@OverRide public void e(Throwable t, String message, Object... args) {
logMessage("ERROR: " + message, args);
Crashlytics.logException(t);
}

private void logMessage(String message, Object... args) {
Crashlytics.log(String.format(message, args));
}}

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-28928963
.

[imminent]

I'm going to close this myself. Thanks

[Turbo87]

That's why I axed it down to four. Error: really bad exception, warning: exception but not that bad, info: app flow and status messages, debug: noisy debug-only info.

I'm using that classification too, but I used to log the HTTP traffic with v() so that it can be filtered easily. I would appreciate it if verbose logging could be added too.