Skip to main content
In a Spring Boot application the starter installs Slf4jNexusLogger, so the SDK logs through SLF4J to the logger named dev.westyx.nexus.NexusClient with no setting - wherever your logging configuration sends that logger’s level.
A plain NexusClient.create(...) without a logger is silent, the Java library norm - except for the startup summary switch below.

What the SDK logs

Every message is collapsed to one line before it reaches SLF4J, so no value can end a log record early and forge the next one.

The startup summary

After the first sync the client logs one INFO record naming what it received:
Names only, never a value. Each list is sorted and capped at 50 names, with a +N more entry after that, so a large service stays one readable line. It is how you confirm from a pod’s log which configs, secrets and flags a deployment actually pulled.
The variable’s name is NexusLogger.LOG_STARTUP_ENV.

Resources the server did not deliver

A sync can report resources it left out - a secret that has no value yet (secret_not_set), a config whose {{secret:KEY}} reference does not resolve (config_unresolved_secret). Such a secret or config reads as absent. Each omission is logged as a WARN the first time it appears; client.getSyncErrors() lists the current ones. nexus.log-sync-errors=false (NexusConfig.logSyncErrors(false)) keeps the list without the log lines.

Secret values never reach the logger

No log record carries a secret’s value, the API key or a session token, and the cached snapshot’s toString() renders counts only. Key names do appear - in the startup summary and in the omission warning. A name identifies what to look up; it is not the credential.

A custom logger

Register a NexusLogger bean and the auto-configuration uses it instead of the SLF4J adapter; for a plain client, pass it to NexusConfig.builder().logger(...).
A logger written without warn still works: its warnings arrive at info.

A different SLF4J logger name

Silencing the SDK

Set the level instead of writing a logger:

A logger that throws is contained

A logger whose method throws never fails an SDK operation. Every internal log call is wrapped, so a failing sink - a broken appender, a full disk - is dropped and the read, refresh, create() or stream thread that logged carries on. The stream observer is contained the same way.