Routes¶
| Route | API | |
|---|---|---|
/ |
landing page, drawn over a D3 force-directed cluster of the default knowledge graph build | knowledge graph |
/stream |
every stream's throughput, success rate and ingest coverage, at a chosen minute / hour / day / month rate | performance |
/stream/:stream/trigger |
trigger conditions for one stream, charted against its history | |
/stream/:stream/alarm |
alarms raised for a stream | datalake |
/data |
each stream's data as it is stored, with its distribution for a chosen month | datalake |
/graph |
every published knowledge graph build, with a picker, a legend and what each build contains | knowledge graph |
/graph/:graph |
the same page, opened on one build, so a build can be linked to | knowledge graph |
/model |
model article listing, with filters and performance | |
/login, /logout, /register, /login/reset |
Cognito-backed authentication | |
/:user, /:user/settings |
account and account settings |
The API column names what a route reads; see APIs. A route without one reads static files, or nothing at all.
The routes are declared in
jsx/import/route/main-route.jsx.
A single unknown segment is not a 404
The route table carries /:user, so an address one segment deep that matches no
other route, such as /no-such-page, renders the account layout rather than the
error page. Only deeper unmatched paths reach the 404. A test pins this as a known
defect; see Testing.