For example, the following message can be found in both the

[CheckReplDBHashInBackground:job0:cd01efc25a775d671bc052a4aabb60b0:CheckReplDBHashInBackground] 2020-10-22T02:41:31.528+0000 Implicit session: session { "id" : UUID("c8f7d847-0405-4afc-b75d-29c5fe5a282f") }

Logkeeper endpoint for the cd01efc25a775d671bc052a4aabb60b0 test case and the CheckReplDBHashInBackground hook.

https://logkeeper.mongodb.org/lobster/build/b6038078fccf68244bbf5d4fd57d3eff/test/5f90f15bf84ae823c55a9638#bookmarks=0%2C9%2C15%2C798858&l=1
https://logkeeper.mongodb.org/lobster/build/b6038078fccf68244bbf5d4fd57d3eff/test/5f90f159c2ab68549c3817ac#bookmarks=0%2C676%2C248981&l=1
https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_inmem_concurrency_simultaneous_replication_add7687fb5fa93ef7366ae808d35f3f90682a407_20_10_21_23_58_48/0

This leads to duplicate log messages when viewing the /all logs endpoint. It also makes the FSM workload log output unnecessarily verbose (although Lobster can hide these messages).