A semantic layer, no free-form SQL
Si picks metrics, dimensions, filters and periods; DataxLand builds the query from versioned definitions; Si runs no SQL of its own when answering.
Connect PagerDuty to ask Si about operational incidents: incident count, P1 incidents, resolved incidents, mean time to resolve and service availability. DataxLand loads incidents, services, priorities and log entries; Si proposes how to read severity, and you approve. When the workspace also has revenue from marketplaces or your website, Si puts downtime next to revenue so you see the business impact.
Free plan with no time limit · No card required · Sample workspace ready in minutes
Example questions Si answers from the metrics below, once the source is connected and the model approved.
| Metric | Definition | Unit |
|---|---|---|
| Incidents | Number of incident-type tickets opened in the period, by open date. | Count |
| P1 incidents | Number of highest-priority incidents (P1, critical) opened in the period. | Count |
| Resolved incidents | Number of incidents resolved in the period, by resolution date. | Count |
| Mean time to resolve (MTTR, hours) | Average hours from open to resolution for incidents resolved in the period.= it_incident_hours_total / Resolved incidents | Number |
| Service availability | One minus outage minutes divided by the service's planned operating minutes in the period.= 1 - Outage minutes / it_planned_minutes | Ratio (%) |
Si picks metrics, dimensions, filters and periods; DataxLand builds the query from versioned definitions; Si runs no SQL of its own when answering.
Standard (pack metric), Approved (workspace metric checked before use), Unconfirmed (exploratory answer, clearly labelled).
In the app, Slack, Telegram, Microsoft Teams or MCP, Si uses the same read-only tools and your permissions in the workspace.
Ask inside the workspace in the language you use; Si answers in the same language, with the metric source and confidence level.
Link your account with a one-time code; ask in a private chat or a group bound to the workspace.
Create an expiring, revocable token (plans with MCP) so Claude, Cursor or your own agent call the same tools.
Choose Add source → PagerDuty and paste a read-only API token for your account.
Si proposes how to read incidents and services and maps them to the pack's standard model; you fix the fields highlighted in yellow, answer the multiple-choice questions and approve the build.
Ask in the app, link Slack or Telegram with a one-time code, or create an MCP token for Claude, Cursor or your own agent.
No. Si only reads the workspace's approved metrics; there is no tool that writes to PagerDuty, and Si never runs its own SQL on your data when it answers.
Yes, through the DataxLand MCP server with tokens that expire and can be revoked. MCP tokens come with the Small Business plan and above; on the Starter plan you ask Si in the app, Slack and Telegram.
Each person must link their DataxLand account with a one-time code and have the Analyst role or higher, and an admin must bind the group to exactly one workspace before Si answers with data.
Every answer names the metrics it used and its confirmation level: Standard for pack metrics, Approved for workspace metrics that passed the number checks, Unconfirmed for exploratory answers.
Connect Pagerduty →Use Si over MCP →
Free plan with no time limit · No card required · Sample workspace ready in minutes