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
We gather logs from the container's standard output (STD) and send them to GRAYLOG. Despite logging everything to STD OUT/ERR during the application's execution, there is currently no mechanism to selectively determine what should be logged. For instance, the log level specified in prod.exs remains static because the runner.exs does not override and cannot be modified with the Docker image. It would be highly beneficial if a dynamic option were available to adjust the log level, providing greater flexibility. Your consideration of implementing such an option is greatly appreciated.
Hi team,
We gather logs from the container's standard output (STD) and send them to GRAYLOG. Despite logging everything to STD OUT/ERR during the application's execution, there is currently no mechanism to selectively determine what should be logged. For instance, the log level specified in
prod.exs
remains static because therunner.exs
does not override and cannot be modified with the Docker image. It would be highly beneficial if a dynamic option were available to adjust the log level, providing greater flexibility. Your consideration of implementing such an option is greatly appreciated.realtime/config/runtime.exs
Line 196 in 7f3aa93
https://github.com/supabase/realtime/blob/7f3aa938e4d3fe6a02f1901facb0a90090df860d/config/prod.exs#L16-L19C1
The text was updated successfully, but these errors were encountered: