Idea ID 2866136
It would be useful if there was a trace level or engine control value you could set on a driver, that would cause the trace level to be effectively 0 but it would still trace the actual XDS right before it is written to eDirectory.
I.e. you will not see the XDS as it moves from policy to policy etc, instead you will only see what actually will be applied to eDirectory before it applied.
It should work both for the regular flow on the publisher channel and also for writebacks from the subscriber channel or for actions that are applied "direct".
That way we could keep a textual log of everything applied that could quickly be searched and we wouldn't have the overhead of tracing all policies and printing of redundant info to the trace.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.