Alex Rousskov wrote:
The intent behind the above two sentences is to allow "higher level"
entities to manage traces for or on bahalf of "lower level" entities.
For example, if an OPES processor uses 100 tiny callout services, the
processor may be configured to remove all callout service entries from
the trace and just insert its own entry (to keep the trace reasonably
small).
It seems to me, however, that in this case, the OPES processor must
still be able to identify those 100 tiny callout services when a user
inquiry arrives later on. It's not sufficient just to know "yes, I did
something to the message and a several services were executed". It's
necessary to know exactly which services were executed. How else would
someone be able to solve possible problems?
This should be spelled out in the document.
It might be a local matter on how this is achieved - one might decide
to maintain the necessary state (well, I probably wouldn't opt for
that option), or maybe the executed services get somehow
encoded/encrypted in the trace entry itself...
-Markus