UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.

Light tracing

Idea ID 2866136

Light tracing

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.

Micro Focus Expert
Micro Focus Expert

I haven't tried it for the special cases, but for the regular flow, you should be able to get the docuement by enabling the audit event


Publisher Filter Transformation Document

Generated after processing the notify filter on the Publisher channel, allowing the user to view the transformed document.

Knowledge Partner Knowledge Partner
Knowledge Partner

I would recommend to extend such a trace level "0.5" with tracing both the incoming event *and* all commands issued on each channel. That way we'd get to see what event triggers processing and the resulting action(s) a driver channel takes.

We've  implemented something similar as a general driver logging addon package years ago, which it turned out to be very useful in understanding and following the event flow between multiple drivers. Wold be great if the engine could provide such functionality instead, since especially handling direct commands from policy can be a bit tricky at times.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.