How to read grouped critical errors instead of treating every log line as a separate problem
Titanium normalizes supported critical errors into fingerprints. Matching failures are grouped so the dashboard can show occurrences, behavior, impact, source lifecycle and the last detection time in one row.
Investigate one grouped error
- Open the Critical error behavior from the last 7 days card.
- Start with the Error column: read the normalized type, message, relative file information and source label when available.
- Check Occurrences to understand how much retained activity belongs to the same fingerprint.
- Read the Behavior badges before assuming a high total means the problem is getting worse right now.
- Use Impact map to see whether frontend or API traffic, background execution or admin activity was associated with the error.
- Use Source lifecycle to compare the error with locally installed component versions.
