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

Come up with a better solution for logging #17

Open
iameli opened this issue Jun 26, 2016 · 2 comments
Open

Come up with a better solution for logging #17

iameli opened this issue Jun 26, 2016 · 2 comments

Comments

@iameli
Copy link
Collaborator

iameli commented Jun 26, 2016

Logging in SK is interesting. We definitely don't want to always log, say, every line of FFMpeg output from every Vertex -- there's just too much there. Or every time a TCP connection happens or anything. It's just too much. Our metadata shouldn't exceed the size of our data.

But I do think it'll be really useful once we're starting to scale up to have the ability flip on verbose logging on an ad-hoc basis. If some particular vertex is behaving strangely, I want SK to tell me every bit of data about that vertex.

Additionally, I don't want this ad-hoc setting to occur over the usual API channels. If the API server is malfunctioning, I want to be able to get very verbose output from it.

@iameli
Copy link
Collaborator Author

iameli commented Feb 10, 2017

Hmmmm yes... I think in development I want everything logging verbosely and we filter on the dev-logs view. end.

@iameli
Copy link
Collaborator Author

iameli commented Feb 10, 2017

Logspout should be fine for logs, we just need something coherent to consume the stream. Elasticsearch? Kibana?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant