Skip to main content

Module trace

Module trace 

Source
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:

Leveltracing levelEvents
0none
1 (default)WARNservant and servant manager panics, failures the application should know of
5INFOconnections opened, accepted and closed; endpoints; LOCATION_FORWARD followed; POAs created and destroyed
10DEBUGeach request and its reply or system exception, client and server; objects activated and deactivated
25TRACEeach 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 level in 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 global tracing subscriber is set, and what the Python binding hands to logging; 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 message that standard error would get: rustorb: <level>: <message>, after the time with set_trace_time. For bindings that write trace lines themselves.
trace_level
The trace level set_trace_level set; 1 at first.
trace_level_of
The trace level of a tracing level: the lowest trace level that selects it.