FAQ

Does BugDNA persist failure data?

No. The built-in tracker and Spring repository are in-memory. Export IDs and aggregates to your existing observability stack when you need historical storage.

Does BugDNA replace stack traces?

No. BugDNA adds stable identifiers to failures. Stack traces are still useful for debugging, while fingerprints make recurring failures easier to group and count.

Does BugDNA parse raw stack traces from log files?

No. The CLI analyses BUGDNA-* IDs that already exist in text logs. Runtime code generates the fingerprints.

Does BugDNA change Spring's error responses?

No. The Spring MVC and WebFlux integrations capture and log failures, then allow Spring's normal exception handling to continue.

Are exception messages part of the fingerprint?

No. Messages are excluded from fingerprint identity to avoid fragmenting equivalent failures across different input values.