Event Debouncing

Because gameplay updates at a very high frequency of 60 times a second or even higher, a debouncing mechanism is in place. Every type of log has its own time slot. If a game triggers too many events of the same type in quick succession, Sentry will only capture the first of its kind, then ignore (debounce) the other events of the same type.

The time that needs to pass after an event has been triggered to be captured again:

  • LogType.Log - one second
  • LogType.Warning - one second
  • LogType.Error, LogType.Exception, LogType.Assert and actual exceptions - one second
Copied
using UnityEngine;

public class DebouncerTestMonoBehaviour : MonoBehaviour
{
    void Start()
    {
        // The time between debug calls of the same type is less than 1s
        // Every following call of the same type gets ignored until 1s has passed

        Debug.Log("Log");              // recorded
        Debug.Log("Log 2");            // not recorded
        Debug.LogWarning("Warning");   // recorded
        Debug.LogWarning("Warning 2"); // not recorded
        Debug.LogError("Error");       // recorded
        Debug.LogError("Error 2");     // not recorded
    }
}
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").