You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2025. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: