Why is 'Active Traces' folder empty for monitored SQL Server instance? (4373700)

Why is 'Active Traces' folder empty for monitored SQL Server instance?

Why is the 'Active Traces' folder empty for a monitored SQL Server instance?

When Auto is set for auditing data collection while configuring SQL Server audit technology within the ApexSQL Audit, it will use the latest available technology:

SQL Server 2005 - Trace
SQL Server 2008 - Trace
SQL Server 2012 - Extended events (Auto), Trace
SQL Server 2014 - Extended events (Auto), Trace
SQL Server 2016 - Extended events (Auto), Trace
SQL Server 2017 - SQL Audit (Auto), Extended events, Trace
SQL Server 2019 - SQL Audit (Auto), Extended events, Trace
SQL Server 2022 - SQL Audit (Auto), Extended events, Trace

For SQL Servers 2017, 2019 and 2022 by default the SQL Audit technology is set and for those instances Active Traces folders should be empty, for other servers where Trace technology is selected those folders will have active traces in it.
This is as designed behavior