Hi Mario, Thanks for the reply. This issue disappeared after I restarted the controller and all related agents. My recall of how this situation came: These auto-discovered BTs of HTTP API server tier used to be masked by an entrypoint BT of the API gateway tier, which is the id=124 BT. After I added a POJO rule to separate the entry point BT into several more meaningful BTs, I DID exclude and delete the original entry point BT. But I still don't understand why the agent continued to hold the context of id=124 BT even after. Is this just a coincidence? Or what is the proper way to exclude the original upstream BT after adding new detection rules? Thanks very much!
... View more