Skip to content
Weik.io
Book a demoTry Weik.io

Product tour

The admin UI shows the integrations, transfers, APIs and channels of your projects with the version that runs in each environment. Every integration and API has its own metrics, traces and logs, and Settings covers the gateways, the agents, the health of the platform and the audit log.

1. Home

Home is the first page after sign-in. It shows each environment with its deployments, and what runs in production with the version of each integration and API and the version devtest runs.

/
The Home page with devtest and production, and the production list with erp-invoice-export, invoice-archiver, the invoices API and supplier-invoices, each at the same version as in devtestThe Home page with devtest and production, and the production list with erp-invoice-export, invoice-archiver, the invoices API and supplier-invoices, each at the same version as in devtestThe Home page with devtest and production, and the production list with erp-invoice-export, invoice-archiver, the invoices API and supplier-invoices, each at the same version as in devtestThe Home page with devtest and production, and the production list with erp-invoice-export, invoice-archiver, the invoices API and supplier-invoices, each at the same version as in devtest

2. Integrations

The Integrations list has every integration of the projects you can see, and the side list filters it by kind. Each row shows the versions that run in devtest and production, and New integration creates one in the browser and shows the weikio init line that writes the same files.

/integrations
The Integrations list with erp-invoice-export, hello, invoice-archiver, the channel invoice-created and supplier-invoices, and their versions in devtest and productionThe Integrations list with erp-invoice-export, hello, invoice-archiver, the channel invoice-created and supplier-invoices, and their versions in devtest and productionThe Integrations list with erp-invoice-export, hello, invoice-archiver, the channel invoice-created and supplier-invoices, and their versions in devtest and productionThe Integrations list with erp-invoice-export, hello, invoice-archiver, the channel invoice-created and supplier-invoices, and their versions in devtest and production

3. An integration

An integration's page shows the version in each environment and the agent it runs on. Under them are the numbers of the last hour, with the integration's own counter among them, and its newest log lines.

/integrations/finance/erp-invoice-export
The page of finance/erp-invoice-export with version 1.2.0 running in devtest on the agent dev and in production on fi-01, the last hour of production with no failed messages, and its log linesThe page of finance/erp-invoice-export with version 1.2.0 running in devtest on the agent dev and in production on fi-01, the last hour of production with no failed messages, and its log linesThe page of finance/erp-invoice-export with version 1.2.0 running in devtest on the agent dev and in production on fi-01, the last hour of production with no failed messages, and its log linesThe page of finance/erp-invoice-export with version 1.2.0 running in devtest on the agent dev and in production on fi-01, the last hour of production with no failed messages, and its log lines

4. Its metrics

Metrics opens on six numbers and a chart of messages with a marker at each deploy, and the memory chart beside it draws the memory setting of the integration.

/integrations/finance/erp-invoice-export/metrics
The Metrics page of finance/erp-invoice-export in production with six numbers, a chart of messages per minute with deploy markers and a memory chartThe Metrics page of finance/erp-invoice-export in production with six numbers, a chart of messages per minute with deploy markers and a memory chartThe Metrics page of finance/erp-invoice-export in production with six numbers, a chart of messages per minute with deploy markers and a memory chartThe Metrics page of finance/erp-invoice-export in production with six numbers, a chart of messages per minute with deploy markers and a memory chart

5. A trace

A trace follows one message through the steps and kamelets of its routes and into the integrations that read its events. Here one invoice goes from export-invoices to the ERP and through the channel invoice-created into invoice-archiver, and each step is a bar with its duration.

/observability/traces
A trace of one invoice: the route export-invoices, the HTTP call to the ERP, the counter, the event to invoice-created and the route of invoice-archiver that wrote the file, each with its durationA trace of one invoice: the route export-invoices, the HTTP call to the ERP, the counter, the event to invoice-created and the route of invoice-archiver that wrote the file, each with its durationA trace of one invoice: the route export-invoices, the HTTP call to the ERP, the counter, the event to invoice-created and the route of invoice-archiver that wrote the file, each with its durationA trace of one invoice: the route export-invoices, the HTTP call to the ERP, the counter, the event to invoice-created and the route of invoice-archiver that wrote the file, each with its duration

6. A transfer run

Each run of a transfer lists its operation, its source and destination and every file it moved. A run that ends with errors raises a problem that links the run.

/integrations/finance/supplier-invoices/runs
One run of finance/supplier-invoices in production that moved three PDF invoices from supplier-ftp:/outgoing to invoice-archive:invoices/incoming with no errorsOne run of finance/supplier-invoices in production that moved three PDF invoices from supplier-ftp:/outgoing to invoice-archive:invoices/incoming with no errorsOne run of finance/supplier-invoices in production that moved three PDF invoices from supplier-ftp:/outgoing to invoice-archive:invoices/incoming with no errorsOne run of finance/supplier-invoices in production that moved three PDF invoices from supplier-ftp:/outgoing to invoice-archive:invoices/incoming with no errors

7. An API's requests

Requests has one row for every call through the gateway, with the version, the subscription, the path and the status. Each row opens the trace of the call.

/apis/finance/invoices/requests
The Requests page of the invoices API in production with filters, a chart of calls and one row for each call from the subscriptions ap-portal, partner-x and partner-yThe Requests page of the invoices API in production with filters, a chart of calls and one row for each call from the subscriptions ap-portal, partner-x and partner-yThe Requests page of the invoices API in production with filters, a chart of calls and one row for each call from the subscriptions ap-portal, partner-x and partner-yThe Requests page of the invoices API in production with filters, a chart of calls and one row for each call from the subscriptions ap-portal, partner-x and partner-y

8. Gateways

Settings › Gateways lists the hostnames each environment answers on, the networks each gateway admits and the APIs and subscriptions it serves.

/settings/gateways
Settings, Gateways, with the devtest gateway on api-test.example.com and the production gateway on api.example.com, each open to callers on the internet and served by the hubSettings, Gateways, with the devtest gateway on api-test.example.com and the production gateway on api.example.com, each open to callers on the internet and served by the hubSettings, Gateways, with the devtest gateway on api-test.example.com and the production gateway on api.example.com, each open to callers on the internet and served by the hubSettings, Gateways, with the devtest gateway on api-test.example.com and the production gateway on api.example.com, each open to callers on the internet and served by the hub

9. Health

Health shows a platform admin every part of the platform with its state and figures, the storage, the gateway instances and the telemetry the hub received, each with what to do when something is wrong.

/settings/health
The Health page with all 10 parts online, no platform problems and the table of parts with the backend, the API gateway, the message server and the storesThe Health page with all 10 parts online, no platform problems and the table of parts with the backend, the API gateway, the message server and the storesThe Health page with all 10 parts online, no platform problems and the table of parts with the backend, the API gateway, the message server and the storesThe Health page with all 10 parts online, no platform problems and the table of parts with the backend, the API gateway, the message server and the stores

10. Audit and access

Every change is an audit record with its actor and the reason given. The Audit log in Settings filters the records by outcome, actor, action and target and shows the weikio audit query line of the same query. Granting access gives a role on a project in chosen environments, down to one integration, and the dialog shows the weikio member add line that does the same.

/settings/audit
The Audit log filtered to deployment changes, with version changes in devtest and production by Anna Virtanen and the reason given for eachThe Audit log filtered to deployment changes, with version changes in devtest and production by Anna Virtanen and the reason given for eachThe Audit log filtered to deployment changes, with version changes in devtest and production by Anna Virtanen and the reason given for eachThe Audit log filtered to deployment changes, with version changes in devtest and production by Anna Virtanen and the reason given for each
The Audit log lists every change with the person who made it and the reason they gave. You filter it by time, outcome, actor and action, and the weikio audit query line above the filters runs the same search.

Open the live demo

The live demo runs integrations and APIs with their traces, and anyone can open it as a viewer.