Skip to main content
The SDK reports through the tracing facade and installs no subscriber of its own - the convention for a library, which leaves the choice of output to the application. Until your application installs one, nothing is printed.

The startup summary

Once create has synced, one INFO event names what the first sync delivered - never a value:
Each list is sorted and holds at most 50 names, followed by +N more. It answers the first question of a misbehaving deployment - did the configuration I expect actually arrive? - without anyone reading a value. With no subscriber installed, set WESTYX_NEXUS_LOG_STARTUP=1 (westyx_nexus::LOG_STARTUP_ENV) to have the same summary written to stderr as one line:
With a subscriber installed the variable adds nothing; the event above already carries the summary.

Resources the server did not deliver

The server leaves out a secret that has no value and a config whose secret reference does not resolve, and says so in the sync response. Each new omission is logged once as a WARN event with code, resource_type, key, secret and detail fields - not again on every poll - and the current list is always available from client.sync_errors(). Set log_sync_errors: Some(false) in NexusConfig to keep the list without the warnings.

What is logged

Spans wrap create, every sync (with its trigger), the session refresh and the write and A/B calls.

What is never recorded

No span field or event carries a secret value, an API key, a session token or a workload OIDC token. Secret key names do appear - the startup summary lists them, and an omission warning names the key it is about - so a line can say which secret it concerns. A permanent test drives every path that touches secret material through a capturing subscriber at TRACE and fails if a value or a credential appears anywhere in the output.