Live Trace Explorer Missing After Jama Connect® Upgrade to 9.28

Sravya Bandari
Sravya Bandari
  • Updated

Published Date: December 8, 2025

Audience: Everyone

Products and Versions Covered: Jama Connect ® version: 9.28.1, Deployment type: Self-hosted - KOTS 

Summary

After upgrading to Jama Connect 9.28, the Live Trace Explorer option is not visible under ADMIN > Organization > Details. This article provides a workaround for this issue. 

The Live Trace Explorer feature flags are not enabled by default after the upgrade to version 9.28, preventing admins from seeing the option to enable it.

Resolution 

To enable the Live Trace Explorer feature, execute the following command:

  • Set a local variable with the TENANT_NAME 
TENANT=$(kubectl describe pod core-0 -n default | grep TENANT_NAME | awk '{print $2}')
  • Check the current output of ff.properties (it should be empty)
kubectl exec -n default core-0 -- sh -c "cat \"/home/contour/tenant/$TENANT/ff.properties\""
  • Manually update
kubectl exec -n default core-0 -- sh -c "printf 'LIVE_TRACE_EXPLORER=true\nLIVE_TRACE_EXPLORER_FILTER=true\n' >> \"/home/contour/tenant/$TENANT/ff.properties\""
  • Recheck
kubectl exec -n default core-0 -- sh -c "cat \"/home/contour/tenant/$TENANT/ff.properties\""
  • Expected output
Defaulted container "core" out of: core, wait-for-search (init), wait-for-database (init), set-filesystem-ownership (init)
LIVE_TRACE_EXPLORER=true
LIVE_TRACE_EXPLORER_FILTER=true

Additional Resources 

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.

 

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.