Dashboard
Live in-memory analytics for API traffic, requests, cache behavior, sessions, queue depth, and configuration footprint.
API Throughput (req/s)
Subroutine Throughput (calls/s)
Queue Depth Timeline
Session Pool Timeline
Cache Live Entries Timeline
Cache Hit Rate Timeline
Top API Endpoints
Top Subroutines
API Method Mix
Configuration Footprint
Request Outcome Distribution
API Status Class Distribution
Hosts
Configure Universe / UniData connections. Each entry defines credentials and the connection pool size.
Add / Update Host
Configured Hosts 0
| Host | Account | Username | Max conn. | RPC timeout | Retries | Logging | |
|---|---|---|---|---|---|---|---|
| No hosts configured yet. | |||||||
Logging
Choose where request logs are written. Per-host logging must still be enabled on the Hosts page.
Log Destination
Invoke traces
Settings for Incoming requests and Outgoing responses. The last 200 invokes are kept in memory only.
Log Fields
Check fields to include, drag to reorder, and click | to place a pipe separator after that field.
Cache Rules
Responses for listed subroutines will be cached for the specified duration.
Add Cache Rule
Cache Rules 0
| Subroutine | Max age | |
|---|---|---|
| No cache rules defined. | ||
Live Requests
Real-time subroutine call feed. New entries appear instantly. Last 200 calls are kept.
Request Log 0
| Time | Subroutine | Host / User | Args | Status | Duration |
|---|---|---|---|---|---|
| Waiting for requests… | |||||
Incoming requests
Authenticated calls to POST /api/invoke/{alias}, newest first. The last 200 are kept in memory and cleared on restart.
Only calls with a valid API key and a valid request body are traced; a rejected key or invalid JSON (422) never reaches the alias and is not shown. Unlike Live Requests, which lists every non-cached subroutine call, this page shows one row per invoke, including cache hits.
Invokes 0
| Time | Alias | Login | Client IP | Domain | Arguments | Status | Duration | Details |
|---|---|---|---|---|---|---|---|---|
| No traced invokes yet. Authenticated alias calls will appear here. | ||||||||
Outgoing responses
How each traced invoke was processed: incoming data, argument conversion, subroutine calls, result parsers, chained calls and the response that went back.
Only calls with a valid API key and a valid request body are traced. Cache hits are included, unlike Live Requests. Values of password, token, secret, authorization, api_key and the sensitive argument names set on the Logging page are masked; secrets inside raw results can't always be recognised.
Cache Viewer
Live entries currently held in memory. Shows cached results and recent errors (kept for 5 minutes).
Cached Entries 0
| Subroutine | Host / User | Args | Result preview | Expires in | |
|---|---|---|---|---|---|
| No cached entries. | |||||
Sessions
Live view of the connection pool. Auto-refreshes every 3 seconds.
Subroutine Definitions
Map JSON arguments to positional subroutine parameters with optional type conversions. Multiple versions per routine are supported.
Definitions 0
| Routine | Ver. | Args | Description | Host | Parser | |
|---|---|---|---|---|---|---|
| No definitions yet. | ||||||
Result Parsers
Map each pipe-delimited field of a raw result string to a named JSON property. Supports nested sub-field splitting.
Parsers 0
| Name | Fields | Item sep. | Description | |
|---|---|---|---|---|
| No parsers yet. | ||||
URL Endpoints
Define URL endpoints that group aliases together. Each endpoint maps to a domain and includes selected aliases.
URL Endpoints 0
| Domain | Description | |
|---|---|---|
| No URL endpoints yet. | ||
Alias Library
Manage alias definitions that map alias names to subroutine definitions.
Aliases 0
| Name | Definition | Description | Timeout | |
|---|---|---|---|---|
| No aliases yet. | ||||
Login
Manage API keys for accessing aliases via the invoke endpoint. Each login gets a unique API key linked to a host.
Configured Logins 0
| Name | Host | Status | API Key | |
|---|---|---|---|---|
| No logins configured yet. | ||||
Config
Export selected items to a JSON file or import a previously exported file to merge data.
Export All
Download a single JSON file containing all subroutine definitions, result parsers, aliases, URL endpoints, and logging configuration.
Import
Upload a JSON export file. Items with matching IDs are updated; new items are appended. Existing items not in the file are left unchanged.