Expand description
Trace output: what the ORB does, for finding interoperability and configuration problems (docs/tracing.md).
The core reports its events through the tracing crate, with the
module of each event as its target (rustorb_core::connection,
rustorb_core::server, …). An application that has set a global
tracing subscriber receives every event and filters them itself.
Without one, the events the trace level selects are
written to standard error, one line each, like omniORB’s
-ORBtraceLevel:
| Level | tracing level | Events |
|---|---|---|
| 0 | none | |
| 1 (default) | WARN | servant and servant manager panics, failures the application should know of |
| 5 | INFO | connections opened, accepted and closed; endpoints; LOCATION_FORWARD followed; POAs created and destroyed |
| 10 | DEBUG | each request and its reply or system exception, client and server; objects activated and deactivated |
| 25 | TRACE | each GIOP message sent and received: type, size and version |
A level includes the events of the levels below it.
Structs§
- Level
- Describes the level of verbosity of a span or event.
Functions§
- level_
name - The name of
levelin trace lines (and in the Python binding). - selects
- Whether the trace level selects events of
level. - set_
trace_ level - Sets the trace level for the whole process (
-ORBtraceLevel N; see the module for what each level selects). It decides what goes to standard error when no globaltracingsubscriber is set, and what the Python binding hands tologging; a subscriber of the application filters with its own settings. - set_
trace_ time - Whether trace lines on standard error start with the time, in UTC
(
-ORBtraceTime 0|1). - stderr_
line - The line for
messagethat standard error would get:rustorb: <level>: <message>, after the time withset_trace_time. For bindings that write trace lines themselves. - trace_
level - The trace level
set_trace_levelset; 1 at first. - trace_
level_ of - The trace level of a
tracinglevel: the lowest trace level that selects it.