Probe behavior
Redaction and capture limits
Understand in-process sanitization, structural bounds, exact-value redaction, and retained evidence limits.
In-process sanitization
Raw captured values are traversed and sanitized inside the target runtime. Only the serialized tree crosses the process or network boundary. Circular values, unsupported types, and values beyond structural limits become explicit truncation markers.
Default structural limits
| Limit | Default |
|---|---|
| Object depth | 3 |
| Array items | 3 |
| Object properties | 50 |
| String characters | 1,024 |
| Stack frames | 8 |
| Retained events per probe | 500 |
Redaction rules
Default key matching is case-insensitive and includes password, secret, token, authorization, cookie, key, signature, SSN, and credit card patterns. Runtime configuration can extend key patterns and add exact, case-sensitive string values.
Generic rules cannot recognize every business identifier or regulated value. Add deployment-specific redaction values and keep watch paths narrow.
Evidence retention
Probe events are stored in a 500-event ring per probe. New events discard the oldest. Removing a probe stops future collection but does not imply immediate destruction of retained audit or diagnostic history.