We need instructions (and probably a nice module) to easily upload logs to cloudwatch. I know there is the cloudwatch daemon, so we might just list that. But having a little node-something can be nice.
Maybe we can just do tail-to-cloudwatch, and be done with it.
See
https://github.com/mirkokiefer/bunyan-cloudwatch
https://www.npmjs.com/package/winston-cloudwatch
mcollina
All 13 comments
I think the easiest way to maintain our priority of performance first is to create this to run separate to the process, as you say like a tail.
Along with that, it could be used for other logging systems also - speaking of which is there no independent thing right now that does this?
davidmarkclements
on 25 Apr 2016
There is the cloudwatch agent: http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/AgentReference.html.
There is no "nodish" thing to do, and no easy way to display those logs from a node point of view.
mcollina
on 26 Apr 2016
This might be helpful: https://github.com/nearform/cloudwatchlogs-stream. However there are a few issues/prs to be handled. cc @mcdonnelldean.
mcollina
on 2 May 2016
@mcollina I've nobody free to put on this right now but I can add it to the list of stuff to look at if you wish?
mcdonnelldean
on 2 May 2016
Is this not solved by pino-socket?
jsumners
on 30 May 2016
Is it? can you put in a little example?
Il giorno lun 30 mag 2016 alle 22:55 James Sumners [email protected]
ha scritto:
Is this not solved by pino-socket?
—
You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub
https://github.com/mcollina/pino/issues/33#issuecomment-222553417, or mute
the thread
https://github.com/notifications/unsubscribe/AADL44uGebOzadiVNgSyEYOzg6LRn1wnks5qG06lgaJpZM4IPFww
.
mcollina
on 30 May 2016
I don't know for sure, though. I've never used that service. But if it just accepts any sort of data on a listening port, then it is solved and the example is already in the readme.
jsumners
on 30 May 2016
I might be able to work on this the following weekend. Not fully sure but I'll try my best. I think our best bet is fix: https://github.com/nearform/cloudwatchlogs-stream and use it here (AKA improve the documentation). Input is welcome.
dgonzalez
on 26 Jul 2016
Just wondering on status of this, what do we need to do to box this off?
davidmarkclements
on 22 Nov 2016
I know this is an old issue, but please feel free to test out this one:
dbhowell
on 21 Sep 2017
Looks great to me (I don't have any way to test it).
Why not use the process.id and hostname from the log lines?
jsumners
on 21 Sep 2017
Originally I was using pid and hostname from the log lines but it means I'd have to parse the input.
By avoiding the JSON.parse() it will work with any text-based log output.
Perhaps an option to do that is worth adding.
dbhowell
on 21 Sep 2017
@dbhowell amazing work, if you'd like to add it to known transports (https://getpino.io/#/docs/transports?id=known-transports) send a PR!
davidmarkclements
on 20 Dec 2018
Related issues
callumlocke
·
4Comments
NicolaiSchmid
·
4Comments
glensc
·
3Comments
yoshuawuyts
·
5Comments
stephenmathieson
·
6Comments
Most helpful comment
Originally I was using
pidandhostnamefrom the log lines but it means I'd have to parse the input.By avoiding the
JSON.parse()it will work with any text-based log output.Perhaps an option to do that is worth adding.