Logging?

[jackfirth]

Inspired by this racket-users thread.

It would be useful to have some loggers for various database connection events to debug database connection issues. For example, logging all queries at the 'debug level or logging connection pool events like when a connection is returned to the pool instead of being closed.

[rmculpepper]

Virtual connections and connection pools do already log their significant events at the debug level.

The other kinds of connections can print debugging information to stderr if you call the *-connect function with #:debug? #t. (That code predates Racket's logging support.)

[jackfirth]

What topic do they log events with? Documentation would be helpful.

More broadly, what's the recommended way for libraries to expose and document their logging facilities? Should libraries make and explicitly provide their own loggers with documentation, or is keeping the logger private and documenting what topic and levels are used enough?

[spdegabrielle]

is this still an issue? Please consider adding the label good first issue so it is findable:

Issues labeled good first issue in in Racket GitHub repositories