Traffic overview_
Every observed request, as it happens. No browser refresh required.
| TIME | CLIENT IP | METHOD | RESOURCE REQUESTED | STATUS | REPORTED BYTES | COUNTRY | SOURCE |
|---|
Threat alerts_
Heuristic findings only. Review activity before deciding to block an IP.
Request explorer_
Query persisted history with server-side filters. Browse older records or export CSV.
| TIME | HOST / IP | METHOD | REQUESTED RESOURCE | TYPE | STATUS | REPORTED BYTES |
|---|
File activity_
Watch reported downloads, image requests, and static asset deliveries.
| FILE PATH | TYPE | HITS | IPs | REPORTED BYTES |
|---|
| TIME | IP | PATH | STATUS | REPORTED BYTES |
|---|
IP intelligence_
Identify repeat visitors and suspicious request patterns.
Investigation queue_
Tracked addresses, analyst decisions, and recent activity. Watch and investigate statuses produce advisory alerts when a monitored IP returns.
| IP | REVIEW STATUS | ANALYST SUMMARY | OBSERVED REQUESTS | LAST SEEN | OPEN ALERTS |
|---|
Incident console_
Curate observed evidence, document investigation decisions, and resolve incidents. No automatic blocks.
Alert quieting_
Temporarily silence new IP-scoped advisory alerts while preserving raw traffic and Cloudflare enforcement. Host-wide findings still appear.
| IP | REASON | CREATED BY | EXPIRES | ACTION |
|---|
Host overview_
Compare observed traffic across monitored sites without assuming complete edge coverage.
| HOST | REQUESTS | UNIQUE IPs | 4XX | 5XX | DOWNLOADS | DECLARED BYTES |
|---|
Deployment lab_
Instrumented observations and operator-reported evidence are separate. No automatic approval and no firewall changes here.
Detection rules_
Fine-tune advisory thresholds without editing Linux files or restarting the process. Changes apply to future events.
Block manager_
Manual IP blocks, status confirmation, and expiration rules.
| IP ADDRESS | STATUS | CREATED | EXPIRES | ACTION |
|---|
Audit history_
Logins, block requests, unblocks, and Cloudflare confirmations.
| TIME | OPERATION | IP ADDRESS | ACTOR | OUTCOME | DETAILS |
|---|
Connection lab_
Prove that a specific website request reaches Sentinel. Each probe is unique, expires after 3 minutes, and never changes firewall rules.
Choose a monitored hostname, start a test, and open the generated URL in another tab or device. A 404 is expected and still counts if the collector observes it.
Confirm that the configured token can read the expected account IP list. This performs a read-only API request and does not modify a block.
| HOSTNAME | SOURCE | 5 MIN | 1 HOUR | 24 HOURS | LAST OBSERVED |
|---|
| HOSTNAME | SOURCE | INSTANCE | PULSE STATE | LAST RECEIVED | COUNT |
|---|
Traffic trends_
Compare traffic observed now with the immediately preceding interval, without counting synthetic demo events. These are requests, not visitors or guaranteed complete site coverage.
Waiting for observations.
Status labels are advisory: Surge requires at least 20 requests in the preceding window and at least double the volume; Server errors requires five or more HTTP 5xx responses and a 10% error share in a current window with 10+ requests. Changes in collector coverage can mimic anomalies.
Operations health_
Verify ingestion, streaming clients, uptime, and database status. This does not prove that every web request is observed.
| HOST | SOURCE | INSTANCE | HEALTH | LAST PULSE |
|---|
No explicit collectors have registered a heartbeat.
Automatic retention is configured through RETENTION_DAYS in your private .env. Back up SQLite before changing it. Pruning is destructive.
Collector healthy means events are reaching Sentinel. Confirm separately that your Worker routes or access logs cover the actual website and that your Cloudflare WAF rule exists before relying on the block manager.
Last observed event and status update automatically every five seconds without a page refresh.