Skip to content
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

jitsu logs follow #245

Closed
grownseed opened this issue May 31, 2012 · 22 comments

Comments

Projects
None yet
@grownseed
Copy link

commented May 31, 2012

I couldn't see this anywhere so I apologize if it's already there, but being able to listen to the logs with jitsu logs would be really nice, instead of being limited to a given number of lines, a bit like tail -f.

@chjj

This comment has been minimized.

Copy link
Contributor

commented May 31, 2012

This a top priority right now. Should be available soon. :)

@grownseed

This comment has been minimized.

Copy link
Author

commented May 31, 2012

Amazing thanks :)

@jfhbrook

This comment has been minimized.

Copy link
Contributor

commented Sep 25, 2012

I just wanted to clarify that this is still in the works.

@missinglink

This comment has been minimized.

Copy link

commented Oct 7, 2012

+1. Also the logs seem to output in reverse order. I would expect the lastest timestamps at the bottom, but they appear at the top

@yawnt

This comment has been minimized.

Copy link
Contributor

commented Oct 7, 2012

The reverse order in the logs has already been fixed in #328

@bdefore

This comment has been minimized.

Copy link

commented Oct 29, 2012

Would love to have the ability to tail the log live. I have noticed that 'jitsu logs' often does not come back with the most recent server output.

@sanderpick

This comment has been minimized.

Copy link

commented Jan 27, 2013

+1 on tail -f functionality!

@grownseed

This comment has been minimized.

Copy link
Author

commented Jan 28, 2013

Not sure this helps but I've put this together. By logging everything to MongoDB on the server side into a capped collection, and then using mongodb's stream() in the 1.2.x driver as well as the tailable option, the output can be sent as and when the collection is updated. Still haven't figured out how to close the streams if the client closes the connection though.

@rcotter

This comment has been minimized.

Copy link

commented Feb 1, 2013

+1

6 similar comments
@acoll

This comment has been minimized.

Copy link

commented Feb 23, 2013

+1

@atuttle

This comment has been minimized.

Copy link

commented Mar 7, 2013

👍

@kaareal

This comment has been minimized.

Copy link

commented Apr 30, 2013

+1

@chadn

This comment has been minimized.

Copy link

commented May 8, 2013

+1

@fredfortier

This comment has been minimized.

Copy link

commented May 9, 2013

+1

@BrandonCopley

This comment has been minimized.

Copy link

commented May 21, 2013

+1

@BrandonCopley

This comment has been minimized.

Copy link

commented May 21, 2013

top priority, 1 yr later?

@holmesal

This comment has been minimized.

Copy link

commented May 29, 2013

+1

1 similar comment
@andreareginato

This comment has been minimized.

Copy link

commented Jun 24, 2013

+1

@julianduque

This comment has been minimized.

Copy link
Contributor

commented Jun 24, 2013

Hello, this will happen soon, we are working on a major infrastructure refactor and this will be included.

@lazywithclass

This comment has been minimized.

Copy link

commented Jul 17, 2013

How is it going? +1

@ahume

This comment has been minimized.

Copy link

commented Aug 6, 2013

+1

@mmalecki

This comment has been minimized.

Copy link
Contributor

commented Aug 16, 2013

Closing this. Implemented with jitsu logs tail in newest jitsu. You need to upgrade your apps with jitsu apps start to make streaming logs available.

image

@mmalecki mmalecki closed this Aug 16, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.