Currently trace configuration is done before service is started. Once service is started, all significant internal components will be created with a wrapper logging it's behaviour to trace writer. Not until the service is shutdown we can't stop it. I suggestion a feature to allow stop tracing during runtime.
Comments: This is a nice idea but is not high enough on the list of priorities at the moment.
Comments: This is a nice idea but is not high enough on the list of priorities at the moment.