Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Kannan Manickam (KannanM3) Idexx Laboratories
Idexx Laboratories
US
KannanM3 Member since 2019 32 posts
Idexx Laboratories
Posted: Dec 11, 2019
Last activity: Dec 12, 2019
Posted: 11 Dec 2019 17:52 EST
Last activity: 12 Dec 2019 10:31 EST
Closed

Tracer on Service REST dont show any trace

I have a service REST and when I try to trace the service calls to see the logs and debug, the tracer works on a general scale but it doesnt show any trace many times and I have to either restart the tracer, refresh the browser, log off and log back in. I have to try multiple combinations of this and it will work sometime and doesnt at times. This is so frustrating while trying to develop the application.

Steps to Reproduce

Environment 1:

1. Open the tracer for 1st service REST and post a call, the tracer will show logs.

Show More

I have a service REST and when I try to trace the service calls to see the logs and debug, the tracer works on a general scale but it doesnt show any trace many times and I have to either restart the tracer, refresh the browser, log off and log back in. I have to try multiple combinations of this and it will work sometime and doesnt at times. This is so frustrating while trying to develop the application.

Steps to Reproduce

Environment 1:

1. Open the tracer for 1st service REST and post a call, the tracer will show logs.

2. Close the tracer, now open the tracer for the 2nd service REST and post a call, the tracer will show logs

3. Close the tracer and open the tracer for 1st service REST again and post a call, now no trace logs will be there

4. Close the tracer and open tracer for 2nd service rest again and post a call, now no trace logs will be there

Environment 2:

1. Open the tracer for an service REST and post a call, the tracer will show logs.

2. Change something in the service REST, save it

3. Close the tracer and reopen it, post a call now no trace logs will be there. This may not happen immediately but happens at one point suddenly so cant gaurantee that it would happen on the first save and reopen of the tracer.

Error Message

No error message just an empty tracer

Attempted Solutions

restart the tracer

refresh the browser

log off and log back in

wait for some time

Any combination of the above sometime helps


Show Less
To see attachments, please log in.
Low-Code App Development Data Integration

Posted: 4 years ago
Posted: 12 Dec 2019 4:16 EST
Leigh Mitchell (Leigh@Labb) Labb Senior System Consultant
Labb
GB

Hey Kannan,

This may be a shot in the dark but what version of Pega are you using and what browser? i remember similar issues but we had a tracer defect fixed with the below hotfix.

https://community.pega.com/support/support-articles/unable-open-tracer

Thanks,

Leigh

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice