How do I calculate error rate?
Errored sessions = sessions with at least one error / all sessions. Errors per session = error events / sessions. In Manalens, errored sessions count errors with severity error or critical; warnings do not count. Compare builds over date ranges of the same length.
Sources: Manalens error tracking documentation.
What is a worked example?
Example numbers: build 571 has 10,000 sessions and 400 of them have an error, so 4% of sessions errored. Build 572 has 10,000 sessions and 900 errored sessions, or 9%. The Top errors table shows that one new SaveFailed error accounts for most of the rise. Fix it before more players reach that save point.
Sources: worked example.
Why does error rate matter for indie PC and web games?
Errors that do not crash the game can still break it: a lost save, a stuck quest or a missing item. Players who meet them early may refund. Valve refunds a game for any reason within 14 days of purchase if the player played less than two hours. Errors are also easy to join to play data, so you can ask whether players who hit an error in level 3 stop playing.
Sources: Steam Refunds policy; Manalens error tracking documentation.
How do I measure error rate in Manalens?
Send error events with track_error() in Godot or TrackError() in Unity. Both SDKs can also capture engine errors and exceptions. The Game health template shows errored sessions, errors per session, errors per session by build, and Top errors with one row per fingerprint. Errors are normal events, so you can use them in funnels, retention and filters.
- Game crash analytics: link crashes to refunds and bad reviews →
- Custom dashboards →
- Game tracking plan generator →
Sources: Manalens error tracking documentation.
Frequently asked questions
Do warnings count in the error rate?
Not in errored sessions. In Manalens, errored sessions count errors with severity error or critical. Warnings do not count, and the SDKs do not capture warnings by default. You can still send warnings and read them in your own charts.
What is the difference between error rate and crash-free rate?
Crash-free rate counts sessions or players with a crash: an unclean exit or an unhandled critical error. Error rate counts all errors of severity error or critical, including ones the game recovered from. A build can keep a high crash-free rate and still have a rising error rate.
How do I send errors from my game?
Call track_error() in Godot or TrackError() in Unity. Both SDKs can also capture engine errors and exceptions for you. The Game health template then shows errored sessions, errors per session, errors per session by build, and a Top errors table with one row for each fingerprint.