[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [opes-end-comm]: What is traceable in an OPES Flow?
On Fri, 29 Aug 2003, jfcm wrote:
> > An OPES entity MAY manage trace entries of entities it
> > controls(?).
> ? "it will be able to authoritatively document
> the tracing queries"
> > For example, an OPES processor may add
> > and/or remove callout service entries.
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). Another example is when an OPES processor knows that a callout
service does not trace itself and adds a callout service trace entry
for that service. Similarly, an OPES system may designate an OPES
processor to remove all tracing entries and ad a single system entry.
I am not sure what you mean by "documenting tracing queries". Do we
talk about "tracing queries" at all anywhere? What are they?
> "remove" or "screen"?
To me, "screen" means "looking at something with the intent to
remove". "remove" sounds more direct in this context. Perhaps I
misunderstood your question.