Running the server for an hour, when idle, will log the following warning:

{"t":{"$date":"2023-03-01T10:53:37.015+00:00"},"s":"W",  "c":"WT",       "id":22430,   "ctx":"thread29","msg":"WiredTiger message","attr":{"message":{"ts_sec":1677668017,"ts_usec":15090,"thread":"5836:0x7fa4acd38700","session_name":"sweep-server","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"WARNING","verbose_level_id":-2,"msg":"Session 13 (@: 0x0x55f142d9fae8 name: EMPTY) did not run a sweep for 60 minutes."}}}

With some GDB investigation, I discovered that this is the always-active session we use to flush the journal , and it is never reset for the lifetime of the server. As is noted in SERVER-31912, this does not cause problems because we never open cursors using this session.

WT-10675 proposes adding an API to set the "name" field that is currently EMPTY, but I'm not sure how we would use that in MongoDB to suppress this warning.