A check says 'what', a log says 'why'
A failed check tells you a problem exists. Syslog records dropped from the device in the same minute often carry the first trace of the cause: an interface going down, an authentication rejection, a memory warning.
Reading these two sources on separate screens lengthens investigation time. Correlating records on a per-incident basis turns the incident into a single timeline.
Source definition and status tracking
Each syslog source is defined; which port it sends data from and whether the stream is continuing are monitored. A source going silent is itself a signal.
This is not a SIEM
The goal here is operational diagnosis: understanding and resolving an outage. Security-event correlation, long-term legal log retention and compliance reporting are outside this scope, and Sentry makes no such claim.