vectordotdev/docs

🌲Timber.io Documentation

docs's Issues

No module named 'timber.TimberFormatter'

It looks like the path to TimberFormatter is off in the docs. When attempting to use the dictionary-based LOGGING configuration (see snippet below), I got the following error:

ValueError: Cannot resolve 'timber.TimberFormatter': No module named 'timber.TimberFormatter'

LOGGING = {
    # ...
    'formatters': {
        'timber': {
            '()': 'timber.TimberFormatter',
        },
    },
    # ...
}

But this worked:

LOGGING = {
    # ...
    'formatters': {
        'timber': {
            '()': 'timber.formatters.TimberFormatter',
        },
    },
    # ...
}

Update certificate file - io.timber-wildcard.pem

Please update certificate file at
https://files.timber.io/certificates/latest/io.timber-wildcard.pem
to RapidSSL RSA CA 2018.
File is outdated.

Integration with winston not work when call debug log level

At now, It's work as expected when I try

const timber = new Timber(TIMBER_API_KEY, TIMBER_SOURCE_ID);
timber.log("Timber some log message");
timber.info("some log message");
timber.debug("some log message");
timber.warn("some log message");
timber.error("some log message");

But It's not working with debug log level when I integrate with winston:

const loggers = new winston.Container();
const timber = new Timber(TIMBER_API_KEY, TIMBER_SOURCE_ID);
this.loggers.add("timber", {
    transports: [new TimberTransport(timber)] as any,
});
loggers.get("timber").info("Hello world from add");
loggers.get("timber").debug("Hello world from add"); // This not work
loggers.get("timber").warn("Hello world from add");
loggers.get("timber").error("Hello world from add");
loggers.get("timber").log({ level: "info", message: "Some message" });
loggers.get("timber").log({ level: "debug", message: "Some message" }); // This not work too
loggers.get("timber").log({ level: "warn", message: "Some message" });
loggers.get("timber").log({ level: "error", message: "Some message" });

Please help fix this. I need this for your cool dashboard

In syslog documentation, mismatch in pem/crt urls

In https://github.com/timberio/docs/blob/master/setup/log-forwarders/syslog.md, rsyslog and "manual" instructions use https://files.timber.io/certificates/latest/io.timber-wildcard.pem, but syslog-ng's instructions involve extra steps to convert from a digicert.com der-encoded crt directly.

It'd make more sense to prefer the timber (really: a redirect?) copy or the digicert copy, not a mix of both among the three syslog instructions.