Changelog
Released changes to the Nolax SDKs and these docs.
SDK 1.1
Released October 2026 for all four SDKs: Node.js @nolax/sdk 1.1.0, Python
nolax-sdk 1.1.1, .NET Nolax.SDK 1.1.0 and Java net.nolax:nolax-sdk 1.1.0.
SDK 1.1 works with the current server and with older servers, which ignore the
fields they do not know.
New options
endpointin every SDKbatchSize,flushIntervalMs,maxQueueSizeandmaxInFlightrelease,serviceandconsumercaptureIp,captureUserAgent,ipHeader,ignorePaths,ignoreMethodsandbeforeSenddryRun, to print payloads without sending them
Delivery
- Defaults change:
batchSize100 (was 20), flush every 2 seconds (was 5), queue of 10,000 events (was 1,000) - Retries use jitter and respect
Retry-After - Sending pauses after a rejected key or a reached plan limit
- Queued events are flushed on shutdown
- Each batch carries
X-Nolax-Batch-IdandX-Nolax-SDKheaders and ameta.sdksummary of dropped events
Fixes
- The Django middleware now runs. In earlier versions it failed to start
- The Django middleware no longer runs a view twice after an error
- Events with a missing IP or User-Agent no longer cause the whole batch to be rejected
- Python worker processes created by
forkkeep sending - The client IP is read from
ipHeaderwhen you set it, so proxies no longer hide the caller - An invalid
environmentvalue is reported instead of being sent
Upgrade notes
- .NET: the undocumented
NolaxSenderandINolaxBatchSendertypes are removed - Node.js and Python:
flushInterval(Python:flush_interval) still works but is deprecated. UseflushIntervalMs(Python:flush_interval_ms)
See Batching and Retries for the full delivery behaviour.
Docs
2026-10-13
- Added Batching and Retries, What the SDK Sends and Verifying the Package
- Config tables for Node.js, .NET and Python now list the SDK 1.1 options
- Corrected the authentication cookie names in the API reference

