Application Crash Trace Normalization Specification

Role: Senior Debugging Infrastructure Engineer with 10 years of experience designing automated crash triage and stack trace sanitization pipelines.

Context

• Client Environment: {{client_runtime_environment}}
• Raw Crash Input: {{crash_payload_format}}
• Trace Sanitization Pattern: {{stack_trace_regex}}
• Deduplication Strategy: {{fingerprint_algorithm}}
• Discard Criteria: {{noise_filter_rules}}
• Target Incident Pipeline: {{alerting_pipeline}}

Task

Author a comprehensive data cleaning and normalization specification that parses incoming {{crash_payload_format}} payloads from {{client_runtime_environment}} into structured, deduped incident objects for {{alerting_pipeline}}.

Method

1. Parse {{crash_payload_format}} payloads to extract error names, memory states, and stack frames.
2. Apply {{stack_trace_regex}} to strip local file paths, machine-specific usernames, and transient memory addresses.
3. Implement symbolication mappings to reconstruct minified or obfuscated source lines.
4. Apply {{noise_filter_rules}} to prune third-party framework frames and benign background exceptions.
5. Compute a deterministic signature using {{fingerprint_algorithm}} based solely on root-cause frames.
6. Normalize operating system, runtime architecture, and device metadata into standard enum keys.
7. Structure cleaned diagnostic metadata into unified JSON incident models.
8. Route unparseable crash payloads to a diagnostic isolation bucket for manual tool inspection.

Constraints

• MUST eliminate all customer filesystem paths and personal user directories from file strings.
• MUST NOT modify the root cause exception message or top-level runtime error code.
• Fingerprint generation MUST produce identical hash outputs across identical root causes.
• Processing pipeline must drop known non-actionable errors matching {{noise_filter_rules}}.

Output format

Format the specification with the following headings:

1. Crash Payload Parsing & Stripping Rules (bulleted list)
2. Stack Frame Cleaning Pipeline (table: Raw Frame Pattern, Transformation, Result)
3. Fingerprinting & Grouping Contract (definition of {{fingerprint_algorithm}} input vectors)
4. Downstream Payload Schema (compact JSON specification for {{alerting_pipeline}}) Keep under 750 words.

Self-review

• Ensure memory addresses and hex pointers are completely stripped by {{stack_trace_regex}}.
• Validate that {{fingerprint_algorithm}} isolates the root cause frame correctly.
• Verify compatibility with the target runtime: {{client_runtime_environment}}.