Question
Morgan Stanley
US
Last activity: 6 Apr 2020 8:03 EDT
How to kill passivated tracer
I am trying to trace service rule. And on re launch of tracer kept come across below message.
Tracer session error: This rule RULE-SERVICE-REST ROBOTICSSSO V1!REGISTER9DE4A97425678C5B1288AA70C1669A64 #20190712T091413.686 GMT is being traced by operator xxxx from requestor HIYxxxxxxxxxxxxxxxxxxxxxxxx - Please restart tracer
on 7.3 used to kill these requestors from SMA->remote tracing->remove watches.
Please advise a way to do same 8.3.1
Pegasystems Inc.
IN
Hi Sashidhar,
Thanks for posting the query. Please try the following approach for this issue.
- Create an activity.
- Add a Java step.
- Add the below code, ((PegaAPI)tools).getSystemOperationsProvider().getListenerManagementAPI().terminateTraceForServiceInCluster("RULE-SERVICE-REST ROBOTICSSSO V1!REGISTER9DE4A97425678C5B1288AA70C1669A64 #20190712T091413.686 GMT ");
- Execute the activity.
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
Please follow the below steps:
1) Switch to Admin Studio.
2) Go to Resources -> Requestors.
3) In the list of Requestors, filter it with Operator ID.
4) On the Requestor row for which you want to terminate trace, click on 3 dots menu and select Terminate Trace. PFB screenshot for more info.
SSA
US
I am also facing the same issue. Why we want to remove manually each time, Is there a Pega agent some cleanup process should take care of these? We also facing the space issues due to this if few developers are running each is consuming around 400MB our temp space is running out.
since it stores the tracer files under server /var/temp/pega/Trace