SQL Trace can highly impact the performance of the server. I can't benefit from trace right now as it's set on any alert to launch a trace.

Other monitoring tools, for instance Sql Sentry, allow the individual alert to be configured with settings for trace.

For example: A long running job might benefit from a trace, while a "dbcc checkdb " hasn't been run in a long time should not trigger a trace. This increases storage and server load for no benefit.

Please look into allowing traces to be configured based on the alert AND the severity level defined on the alert (for example trace on the medium level or higher of long running query, but not when just a low priority level)