a year ago
project id: 271ed33d-be6b-40ce-96ba-504a94362dac
howdy y'all. I'm hosting a go app on railway and it's been great but whenever I use go's default logger or charm log, all of my logs show up as errors instead of info. I have tried modifying the default logger's output to ensure it's not printing to standard err but it's still categorizing all of my logging as errors. Just wondering if anyone has any insight as to why this is happening.
45 Replies
a year ago
you are on the right track, sending logs to stdout instead of stderr would print them as info, can you please provide a minimal reproducible example for me to test
a year ago
sounds good!
a year ago
what version of go do you use
i tried both log.Default().setOutput() and log.setOutput() and both seem to send to stderr anyways
a year ago
is cmp.Or a thing in that version?
a year ago
little tip but it has nothing to do with logs - port := cmp.Or(os.Getenv("PORT"), "8080")
saves 3 lines haha
a year ago
okay ill get to testing now
a year ago
well not off to a good start

okay so it looks like you just can't set the default logger's output to stdout
a year ago
i was just about to say that lol
but making a new logger with stdout as its output seems to fix the problem
a year ago
i was also going to say that lol
a year ago
as a go dev myself, may i ask why charm?
if i'm being serious it's mostly that i appreciate them having a lot of different log levels that are visually differentiated instead of just either crashing the program or not
a year ago
are you planning on using the json logger?
a year ago
this was all done with stdlib slog

a year ago
this is what can be done with json logging on railway
oh that's pretty interesting. I might look into implementing that down the line
this is just my personal site so right now I'm just trying to do basic request logging middleware that doesn't turn my whole log page red lol
a year ago
sounds good
a year ago
no problem!
interesting postscript to this: it looks like my original fix actually was working for some logs but not others. I'll have to do some digging to see what's different between them
a year ago
charm doing some weird stuff then eh
my original fix totally worked: it redirected all of the charm logs to stdout instead of stderr
but my logging middleware was using stdlib log instead of charm log, so it didn't apply to those
a year ago
haha okay that's funny
a year ago
awesome