-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update version to 2.0.0 #95
Comments
@kenperkins @troy @ffxsam Any update on this? |
@1212gmartinez: I'm no longer a maintainer, but @markdascher may have some comments. |
Ditto, I'm no longer using Papertrail. |
@kenperkins @markdascher any update on this? |
I'd have to dig back in and refresh myself on this project. I haven't touched any of these in quite some time. |
I started looking into this again, but came across an alternative that might actually work better. The winston-syslog transport is maintained by winston contributors, already built for v3, and recently added TLS support. I just tried it out, and it worked well: const os = require('os');
const winston = require('winston');
require('winston-syslog');
const papertrail = new winston.transports.Syslog({
host: 'logsN.papertrailapp.com',
port: XXXXX,
protocol: 'tls4',
localhost: os.hostname(),
eol: '\n',
});
const logger = winston.createLogger({
format: winston.format.simple(),
levels: winston.config.syslog.levels,
transports: [papertrail],
});
logger.info('hello papertrail'); In other news, Papertrail recently added native HTTPS ingestion support, so if you just need to send in JSON logs, Winston's native Http transport would also work: const winston = require('winston');
const papertrail = new winston.transports.Http({
host: 'logs.collector.solarwinds.com',
path: '/v1/log',
auth: { username: new String(''), password: 'TOKEN' },
ssl: true,
});
const logger = winston.createLogger({
transports: [papertrail],
});
logger.info('hello papertrail'); @1212gmartinez can you see if one of these transports works for your purposes? |
Winston version 3.0 has been out for over 2 years at this point. It seems that the v2 branch of this repo works with winston@^3.0.0.
Is is possible to merge the v2 branch to master and update the version?
The text was updated successfully, but these errors were encountered: