Using SQL Compliance Manager 5.6 with SQL Server 2016 and older servers, the SQL Server error log gets flooded by messages such as:
SQL Trace ID 3 was started by login "CORP\SOME_LOGIN".SQL Trace stopped. Trace ID = '3'. Login Name = 'CORP\SOME_LOGIN'.
The login referenced is the service account we are using for SQL Diagnostics Manager, and is included in the Trusted Logins on the server config.
We have the collection method set to Extended Events, but apparently that method doesn't apply to some things, or there is a bug.
The Extended Event collection option is limited to the collection of SELECT and DML events. All other audit settings (e.g. Admin, Security, DLL, etc) are still reliant on SQL Server Profiler Traces in the current release of SQL Compliance Manager. On that note, the log entries that you mentioned in the SQL Server Error Log are expected.
On another note, if you take a look at the Windows Application Event Log in Event Viewer, you'll also see similar entries. If you use the "-n" startup parameter, SQL Server error logging will not be performed to the event log. Be aware that this will also prevent the logging of other SQL server errors as events, including successful and failed backups. If you need to see this information, you can still find it in the SQL Server error log , located at "C:\Program Files\Microsoft SQL Server\MSSQL\LOG" by default.
For more information, please see the Microsoft Books Online article on Startup Parameters.Unfortunately, I'm not aware of any option to prevent SQL Server from logging the trace related activities into the error logs.