01
Request-level records
Request logs include connection details, delivery status, Hyx AI decisions, and serving time.
Product plane / Observability
Observability
operationalTrace a request from connection to enforcement.
Each delivery, security, and Hyx AI decision is saved in one searchable request record, along with the serving location. Teams can investigate one timeline instead of combining separate exports.
- 60+
- request details
- Delivery, security, identity, and Hyx AI context.
- 28
- built-in signals
- Recorded with minimal request overhead.
- 1 row
- per request
- A single attributable record across the pipeline.
- live
- operational visibility
- Network, Hyx AI, traffic, and security trends.
01 / proof
02 / proof
03 / proof
04 / proof
Core capabilities
Request context stored in one record.
Hyx records what arrived, how it was classified, which controls ran, and why the final action occurred. The same record supports security review, performance diagnosis, and traffic analysis.
OBS-01 / attributable request record
one request / one row
Schema width
60+
dimensions / request
Delivery, identity, security, Hyx AI, and serving-location details appear together.
Request details
live view
01Connectionmethod · security · identity8
02Requestmethod · path · host · bytes12
03Deliverystored · server · speed9
04Identityip · asn · country · bot_score7
05Securityrule · protection · action8
06Signalsactor_window · named flags6
07Hyx AIversion · confidence · reasons7
08Fleetpop_id · config_version · node5
Join jobs
0
context written together
Attribution
1 ID
connection through enforcement
Availability
Live
fleet and traffic trends
02
Traceable block decisions
Block records show the trigger, Hyx AI version, and location that handled the request.
03
Point-and-click traffic queries
Explore traffic history from the dashboard with a safe point-and-click query builder.
04
Attack classification
Built-in detectors label suspicious behavior such as SQL injection, Log4j probes, and login attacks.
05
Find and fix false alarms
The dashboard highlights frequently triggered rules with low confirmed value for review and tuning.
06
Traffic and security dashboards
Share dashboard views of traffic, security, bots, origin health, and day-over-day trends with your team.
How it works
Connect request, visitor, Hyx AI, and network data.
Lightweight observations build a recent visitor history, inform firewall and Hyx AI decisions, and appear beside the final action for later analysis.
OBS-02 / signal registry
observe first / decide later
Built-in signals
28
- Emit
- zero alloc
- Window
- lock free
Registry topology
01020304050607080910111213141516171819202122232425262728
01InjectionSQLI · XSS · LFI · RFI · CMDI · LOG4J
02ReconSCANNER · suspicious extension · path intent
03AuthenticationAUTHFAIL · velocity · retry shape
04CorroborationATTACK-REQS · ATTACK-FLAG · sticky evidence
observe → compare with recent behavior → inform policy and Hyx AI → attach the decision
- 01
Capture
Record delivery, server, identity, security, and Hyx AI details under one request identifier.
- 02
Observe
Name suspicious activity such as injection, scanning, login abuse, and unusual behavior.
- 03
Connect
Combine the request with recent visitor activity, active policy, Hyx AI version, and serving location.
- 04
Explore
Query incidents, trends, false positives, speed changes, and Hyx AI behavior from the same data.
Operational detail
Capabilities included with Hyx.
A concise list of what this part of Hyx provides. Roadmap items are labelled explicitly.
Included
10Request-level records
Traceable block decisions
Point-and-click traffic queries
Attack classification
Find and fix false alarms
Traffic and security dashboards
Origin health summary
A built-in assistant for your dashboards
Full control over your AI protection
Background operations status
Next system / Platform
Manage sites and network locations from one dashboard.
See how sites, certificates, live configuration, fleet history, deployment, and managed tooling fit together.