Profiler trace it includes Service Broker events, for XEvents it does not

[gambit9009]

Service Broker issues might be rare, but having an event enabled that doesn't add overhead to the capture would be helpful to have. Thought would be if we collected it in Trace, probably we should get it in XEvent by default.

For Trace we would get Broker:
Connection
Corrupted Message
Forward Message Dropped
Message Undeliverable

[PiJoCoder]

The ask is to get SQL Trace and Xevent at par - make the same defaults - in General and Detailed Scenarios

Xevents:
broker_corrupted_message
broker_forwarded_message_dropped
broker_message_undeliverable

broker_connection does not exist in XE

[PiJoCoder]

Already added to SQL LogScout 281