Hello community,  I encountered a problem with BT exclusion.  I configured a rule (scope is good) to exclude a BT from automatically being discovered: URI contains 'socket'. The config is present in the transaction.xml file of my agent:  <servlet-entry-points enabled="true"> <custom/> <automatic-transaction-discovery enabled="true" resolution="first-entry-point"> <excludes> <exclude name="SocketExclude"> <servlet-rule> <enabled>true</enabled> <priority>2</priority> <excluded>false</excluded> <uri filter-type="CONTAINS" filter-value="/socket"/> </servlet-rule> </exclude> but the agent is still registrering BT :  [AD Thread Pool-Global19] 10 Feb 2020 16:42:16,542 INFO BusinessTransactionRegistry - Registered BT Name[/myapp/socket/750/oa4riml3/xhr_streaming], Id[540] [AD Thread Pool-Global19] 10 Feb 2020 16:42:16,542 INFO BusinessTransactionRegistry - Registered BT Name[/emyapp/socket/info], Id[541] [AD Thread Pool-Global19] 10 Feb 2020 16:42:16,542 INFO BusinessTransactionRegistry - Registered BT Name[/myapp/socket/750/gxqnx3vy/websocket], Id[542] And I find them in the controller. Am I doing something wrong?  Besides I cannot exclude manually in the BT screen because par 3 and 4 of the URI are dynamic.  Thank you ... View more