WebCheck stores bounded evidence so you can understand a result without turning every monitoring run into a copy of the target website. The exact fields depend on the check type and configured assertions.
Common run metadata
Completed runs can include status, start and finish times, duration, time to first byte, response size, HTTP status, redirect count, error classification and the final URL.
Check-specific evidence
HTTP and content checks can store content hashes and configured assertion results. DNS checks store normalized supported records and a record hash. TLS checks store certificate subject, issuer, SANs, validity, expiry, TLS version and cipher details. TCP checks store connection timing and classification.
Boundaries
WebCheck does not need to store cookies, authorization headers, form values or complete response bodies by default. Content assertions should use only the minimum stable text needed to answer the monitoring question.
How to use the evidence
Use the evidence to compare a failing run with preceding and recovery runs. It is diagnostic context about the monitored request, not a complete copy of the application state or a replacement for server logs.