4 ms·
Wow, this is exactly what I’ve been missing—juggling a dozen kubectl logs windows and still losing context. Seeing all container logs merged in real time is a g
by carlgreene 1y ago
Wow, this is exactly what I’ve been missing—juggling a dozen kubectl logs windows and still losing context. Seeing all container logs merged in real time is a game-changer for debugging multi-pod workloads. Love that it runs locally against the API—no more sending sensitive logs offsite. Big thanks to the author for saving my sanity here!
- andres 1y agoThanks! Your comment made my day! It sounds like your use-case is similar to mine when I started working on the project. Now we have a community of contributors working on Kubetail so if you have time, stop by our Discord and let us know what else we can do to help (https://discord.gg/CmsmWAVkvX https://discord.gg/CmsmWAVkvX).
- biot 1y agoWhile the search offered is handy, I watch logs on multi-pod workloads via: kubectl logs -f -l app=api --max-log-requests=50 This follows along all pods with the given label (app: api) for up to 50 pods or however many you want. Quite useful when I'm looking for specific output such as ERROR logs to just pipe it to grep like this: kubectl logs -f -l app=api --max-log-requests=50 | grep ERROR and get realtime filtering of all log output without having to tail individual pods by name.