Railway•5mo ago

go logging registers as errors

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.

Solution:

but making a new logger with stdout as its output seems to fix the problem

Jump to solution

36 Replies

Percy•5mo ago

Project ID: 271ed33d-be6b-40ce-96ba-504a94362dac

Brody•5mo 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

sowingOP•5mo ago

yeah i'll whip one up when i get back to my computer

Brody•5mo ago

sounds good!

sowingOP•5mo ago

ok i think this should do it

package main

import (
  "os"

  "github.com/charmbracelet/log"
)

func main() {
  log.Default().setOutput(os.Stdout)

  port := os.Getenv("PORT")
  if port == "" {
    port = "8080"
  }
  log.Infof("Listening on port: %s", port)
}

package main

import (
  "os"

  "github.com/charmbracelet/log"
)

func main() {
  log.Default().setOutput(os.Stdout)

  port := os.Getenv("PORT")
  if port == "" {
    port = "8080"
  }
  log.Infof("Listening on port: %s", port)
}

Brody•5mo ago

what version of go do you use

sowingOP•5mo ago

i tried both log.Default().setOutput() and log.setOutput() and both seem to send to stderr anyways 1.22

Brody•5mo ago

is cmp.Or a thing in that version?

sowingOP•5mo ago

it is indeed

Brody•5mo ago

little tip but it has nothing to do with logs - port := cmp.Or(os.Getenv("PORT"), "8080") saves 3 lines haha

sowingOP•5mo ago

that's pretty nice. never used that before lol

Brody•5mo ago

okay ill get to testing now

sowingOP•5mo ago

thanks so much!

Brody•5mo ago

well not off to a good start

sowingOP•5mo ago

oh that's totally my bad no lsp in discord code blocks capitals for public methods is right. I've been writing too much rust okay so it looks like you just can't set the default logger's output to stdout

Brody•5mo ago

i was just about to say that lol

Solution

sowing•5mo ago

but making a new logger with stdout as its output seems to fix the problem

sowingOP•5mo ago

so i'll just have to make that work should be fine

Brody•5mo ago

i was also going to say that lol

sowingOP•5mo ago

thanks so much for your time on this lol

Brody•5mo ago

as a go dev myself, may i ask why charm?

sowingOP•5mo ago

pretty colors 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

Brody•5mo ago

are you planning on using the json logger?

sowingOP•5mo ago

i wasn't aware there was going to be one

Brody•5mo ago

this was all done with stdlib slog

Brody•5mo ago

this is what can be done with json logging on railway

sowingOP•5mo ago

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

Brody•5mo ago

sounds good

sowingOP•5mo ago

thanks for helping out again :)

Brody•5mo ago

no problem!

sowingOP•5mo ago

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

Brody•5mo ago

charm doing some weird stuff then eh

sowingOP•5mo ago

i figured it out and this is incredibly silly 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

Brody•5mo ago

haha okay that's funny

sowingOP•5mo ago

just pushed the change and everything is showing up blue!

Brody•5mo ago

awesome

Gaming

Programming

go logging registers as errors