Hi everyone,
I’m currently developing and debugging the Container Service plugin within an XNAT deployment running on Kubernetes.
At the moment, every time I add a new debug() line in the Java code, I have to rebuild the plugin JAR, redeploy it into the XNAT environment, and then check the updated containers.log inside the pod (via kubectl exec).
This workflow is very time-consuming. I’m wondering if there’s a better way to view new DEBUG log outputs in real time without rebuilding the plugin each time.
Specifically:
Is there a recommended way to dynamically change the logging level for the Container Service (e.g., via containers-logback.xml, JMX, or another mechanism)?
Can I reload or hot-update the log configuration (e.g., set scan="true" in logback.xml) while XNAT is running?
Alternatively, are there best practices to stream live logs from the Container Service during development or to hot-swap new code for testing without a full rebuild?
Any advice or example configuration from others who develop XNAT plugins in similar environments (e.g., Docker or Kubernetes) would be greatly appreciated.
Thanks in advance,
Chenxi
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/0654d18c-d18d-4236-bc27-298c6a8e2f81n%40googlegroups.com.
--
To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/CAHPNenserLr9X%3Dc6Mv%2BewM%2BRQa0UQB631GAiKFaLporfyQUqkw%40mail.gmail.com.
To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/CAGH9FAyK0kj-VOrt8u-rt_RUw9RNwOfLGzZYFFvJSPnPeAnSfA%40mail.gmail.com.
To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/CADwXCSqSPYd6LPetTaG1g4JcwW_K1bySjc%3Dpr3noiB4XvWh_UQ%40mail.gmail.com.