Haha RTFM - didn’t even cross my mind!
The job is called
SQLWATCH-LOGGER-WHOISACTIVE but I actually dropped support for WhoIsActive in recent versions. I can’t recall which version exactly, was just trying to find a reference on GitHub but can’t. In summary, the justification was that
WhoIsActive provides very little benefit with the way it was being used in SQLWATCH. There are other methods in SQLWATCH to collect the same information in a more reliable way such as Extended Events.
That’s not to say
WhoIsActive isn’t good - it’s brilliant but just not what I needed. As an example, if you run it every 15 seconds to collect your workload, there could be a lot happening between collection points and you could lose a lot.
Having said that, if you really want it back, you can do. If you just give me your SQLWATCH version I will try work out what you need to do.