Something I've noticed is that I am having to look at production systems manually to do debugging alongside the logs which just made me wonder how other people were doing it
Ask HN: How often do you investigate issues in production vs. looking at logs?
1–10 of 10 posts
Re: Ask HN: How often do you investigate issues in production vs. looking at logs?
#21. the logs hopefully tell you where to look
2. the logs hopefully give you enough context to construct a physical test (ie, replicate)
3. the physical test hopefully gives enough context to write an automated test
4. we write the automated test, submit to staging, do the physical test again
5. PROFIT!
Re: Ask HN: How often do you investigate issues in production vs. looking at logs?
#3In my experience logs are rarely enough for browser automation issues.
I usually end up reproducing the actual session manually because timing/state problems often don’t show up clearly in logs.
Re: Ask HN: How often do you investigate issues in production vs. looking at logs?
#4we don't lol, we used to do but these day everyone is doing vibe coding and nobody looking at the logs or error but i use sentry for my side project
Re: Ask HN: How often do you investigate issues in production vs. looking at logs?
#5Certain bugs don’t really make sense until you interact with the real system
Re: Ask HN: How often do you investigate issues in production vs. looking at logs?
#61. the logs hopefully tell you where to look 2. the logs hopefully give you enough context to construct a physical test (ie, replicate) 3. the physical test hopefully gives enough context to write an automated test 4. we write the automated test, submit to staging, do the physical test again 5. PROFIT!
PROFIT BABYYY
Re: Ask HN: How often do you investigate issues in production vs. looking at logs?
#7we don't lol, we used to do but these day everyone is doing vibe coding and nobody looking at the logs or error but i use sentry for my side project
yeah time to pipe it into claude and tell me what is wrong
Re: Ask HN: How often do you investigate issues in production vs. looking at logs?
#8In my experience logs are rarely enough for browser automation issues. I usually end up reproducing the actual session manually because timing/state problems often don’t show up clearly in logs.
yeah those are especially nasty. the logs are cryptic and not helpful when most of the the issues will be seen visually in the browser
Re: Ask HN: How often do you investigate issues in production vs. looking at logs?
#9Certain bugs don’t really make sense until you interact with the real system
yeah that's kinda how I feel but wanted to see other's experience