npm / @nestjs/observe

@nestjs/observe

What changed in @nestjs/observe 0.3, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-20.

1 security4 new APIs and options2 performance4 behavior and defaults14 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@nestjs/observe 0.325 changes

The JWT redaction rule is now linear and also applies to error messages and request bodies captured with http.capture.body.
0.3.11release notes

Custom request operation ids are supported.
0.3.13release notes
An enabled option can switch the agent off.
0.3.13release notes
Database queries for MSSQL (SQL Server) can be instrumented.
0.3.13release notes
The collector is told which ingest modes the agent can read.
0.3.12release notes

Parsing forwarded log lines now takes linear time regardless of input, avoiding event-loop delays from long runs of whitespace.
0.3.11release notes
Nest's Reflector is no longer instrumented, avoiding spans from repeated metadata lookups that added no insight.
0.3.11release notes

While an account's overage is paused, only server errors are sent.
0.3.13release notes
Rejected credentials are no longer retried on every flush.
0.3.12release notes
Forwarded log metadata is constrained to collector limits: context is redacted and capped at 255 characters, trace ids are validated, and levels are mapped to Nest's.
0.3.11release notes
JSON logs from winston, pino and similar loggers map info, warning and trace to Nest levels; other levels are kept as attributes.level.
0.3.11release notes

Driver copies nested in Prisma's pg adapter and other dependents are patched.
0.3.13release notes
A paced Free day is distinguished from a spent allowance.
0.3.12release notes
When the collector rejects a batch for an invalid or oversized value, the agent removes just that value or entry and resends the rest instead of dropping the batch.
0.3.11release notes
The JWT rule no longer matches a token directly preceded by a hyphen; the token= and Bearer rules are unchanged.
0.3.11release notes
maxTracesPerBatch is capped at 5000, the collector's maximum accepted batch size.
0.3.11release notes
The notice now states what data is still kept, and a new notice covers trimmed traces on paid plans.
0.3.11release notes
A trace id is read from a log line only if it matches [A-Za-z0-9._:-]{1,128}; otherwise the line uses the trace id of its request.
0.3.11release notes
Forwarded VERBOSE lines now carry their level and context.
0.3.11release notes
Buffered telemetry is flushed before the worker shuts down.
0.3.10release notes
Trace arrays are preserved during degraded ingestion.
0.3.10release notes
Instances without a constructor continue to work.
0.3.9release notes
Instrumented methods return the original promise.
0.3.9release notes
Async hooks symbols are ignored when distinguishing a plain promise, improving promise detection.
0.3.9release notes
Plain promises are chained so a dropped rejection still surfaces.
0.3.9release notes