Request: Support cleanup/deletion of BT's as part of a deployment including BT lockdown configuration.
Imagine this workflow.
Customer installs Java APM agent and instruments thier application. Like the good agent that it is, it starts auto detecting lots of servlet BT's out of the box. And looks like this
They then run their automation tool uploading/setting up the real first class BT's they want, all good, but now the old BT's are still there.
If we support deletion/truncation of BT's as part of the tool then we can clean up/delete all BT's for that App as part of the deployment (if they aren't in our configBT.json file), resulting in only the first class BT's we configured in the configBT.json being visible in our Business Transaction List.
(We would also need to support turning on BT Lockdown as a config item)
Request: Support cleanup/deletion of BT's as part of a deployment including BT lockdown configuration.
Imagine this workflow.
Customer installs Java APM agent and instruments thier application. Like the good agent that it is, it starts auto detecting lots of servlet BT's out of the box. And looks like this
They then run their automation tool uploading/setting up the real first class BT's they want, all good, but now the old BT's are still there.
If we support deletion/truncation of BT's as part of the tool then we can clean up/delete all BT's for that App as part of the deployment (if they aren't in our configBT.json file), resulting in only the first class BT's we configured in the configBT.json being visible in our Business Transaction List.
(We would also need to support turning on BT Lockdown as a config item)