Add your app to the command centre
Your app can put its own information and actions where people already work in Xovris: a link from an incident to the same problem in your tool, a form whose answer lands on the incident’s timeline, your view of a server or a site, a review of a change your tool proposes, or a whole app in a sealed frame.
Every component is a small JSON object. Xovris checks it against the schema before it is shown, and a component that fails says which field is wrong and offers a retry - it is never silently left out.
The eight kinds
Section titled “The eight kinds”| Kind | kind | Where it appears | Fields |
|---|---|---|---|
| Issue link | issue_link | Beside an incident’s title | label, href, reference? |
| Status badge | status_badge | Beside an incident’s title | label, tone |
| Alert action | alert_action | With the choices on an incident | label, description?, fields |
| Fix review | fix_review | Under an incident’s fix | change, reason, evidence, test, expectedEffect, wayBack, href? |
| Timeline entry | timeline_entry | In an incident’s timeline | at, text, href? |
| Asset panel | asset_panel | On a connection’s page | rows, href? |
| Settings page | settings_page | In developer settings | fields |
| App in a frame | app_frame | On a page of its own | src, height? |
Every component also carries an id (yours, up to 80 characters) and a title (shown as its heading, up to 80
characters). Every address must start with https:// and must not carry a user name or password.
The schema
Section titled “The schema”The full JSON Schema (draft 2020-12) is published at
/schemas/extension-component.json. Validate against it in your own tests; it is
generated from the same definition Xovris checks with, so a component that passes it passes in the command centre.
{ "id": "deploy-412-review", "kind": "fix_review", "title": "Roll back deploy 412", "change": "Roll back deploy 412 to deploy 411", "reason": "The checkout errors began two minutes after it", "evidence": ["5xx responses rose from 0.1% to 9% at 10:02"], "test": "The checkout journey passes 3 of 3 runs", "expectedEffect": "Errors fall back under 0.1%", "wayBack": "Redeploy 412"}A fix review always says the six things a person needs before trusting a change: what changes, why, the evidence, the test that proves it, what should happen, and the way back.
A whole app in a frame
Section titled “A whole app in a frame”An app_frame opens your app on a page of its own inside the command centre. It runs sealed off from Xovris: it is
always served from your own address (never Xovris’s), it stays inside its own frame – the page around it is never in its reach – and it
never acts as the person using it.
Your app and Xovris talk only through postMessage, and only from your app’s own origin:
| Your app sends | Xovris answers |
|---|---|
{ "type": "xovris:ready" } |
{ "type": "xovris:init", "theme": "dark", "tokens": { "role": {...}, "space": {...}, "radius": {...} } } - the person’s theme and Xovris’s design tokens, so your app matches; sent again whenever the theme changes |
{ "type": "xovris:resize", "height": 640 } |
the frame takes that height, between 120 and 2,000 pixels |
{ "type": "xovris:notify", "text": "Board synced" } |
the text is shown above your app, up to 240 characters |
Any other message is ignored.
Where people find your app
Section titled “Where people find your app”Everything added to a workspace is listed under Settings, Developers, Apps in the command centre, with whether each component passed the schema and where it appears.
Your data is never used to train our AI. How your data is kept
A problem is called fixed only once it works again. How each fix is checked
XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.