Skip to content
Log inContact sales
CopilotQuestions with citations, in Thai or EnglishWorked example · INC-20931

Ask in Thai or English. Get answers with citations.

Operators ask what they would ask a colleague: “Is this the vendor or us?” The copilot investigates with the same tools and permissions as the person asking, and cites every claim. It will not show a viewer data their role cannot see.

Tools

The copilot uses the same permission-checked tools as the console.

The copilot investigates through five tools: logs, metrics, incidents, topology and runbooks. Permissions are enforced in the tools, not in the prompt, so a question cannot widen access.

Copilot tool calls · INC-20931as Narin S. · operator
  1. metrics.query("payments-gw", "http_5xx", last 30m)
    Allowed for the role
    5xx at 31 %
  2. logs.search("order-api", "upstream timeout", last 4m)
    Allowed for the role
    1,284 lines · already masked at ingestion
  3. incidents.get("INC-20931")
    Allowed for the role
    7 alerts grouped · cause assessment attached
  4. topology.path("checkout-web", "payments-gw")
    Allowed for the role
    errors confined to the payments-gw path
  5. runbooks.read("payments-gw", lang)
    Allowed for the role
    RB-PAY-004
5 toolslogs, metrics, incidents, topology, runbooks
Fig. 1 — The same permission-checked tools as the console. The role is checked on every call, and the copilot reads data only through these bounded tools.
Citations

Every claim cites evidence.

Each factual statement cites a tool result or a runbook passage, and each citation reopens the result it came from. If the copilot cannot find evidence, it says so rather than answering from general knowledge.

Is this the payment provider or us?

Most likely the provider. payments-gw has returned 5xx on 31 % of calls since 14:01:58 , and its status page reports degraded card authorisation . order-api is healthy on every other dependency and has had no changes in 24 hours . Recommended next step: fail over card payments to the secondary provider.

Every claim cites evidence. Answers respect the asker’s role.

Evidence behind the answer

  1. 1Metric ·payments-gw 5xx responses 31 % (baseline under 0.5 %) since 14:01:58
  2. 3Status ·Provider status page reports degraded card authorisation since 13:59
  3. 4Topology ·order-api healthy on every other dependency; errors confined to the payments-gw path
  4. 5Change ·No deploys or configuration changes to order-api in 24 h
Fig. 2 — Hover or focus a reference to find its evidence. Each reference reopens the result it came from, authorized again for the person opening it.
Refusal

A refusal comes with an alternative.

A viewer who asks for data their role cannot see is refused with an alternative they can see. The copilot will not show a viewer data their role cannot see.

User (viewer)

Show me the raw payment logs for card ending 4417.

Copilot

You don't have access to raw payment logs. I can show the masked error summary for payments-gw instead.

Restricted request
The copilot refuses, and offers an alternative the role can see.
No evidence found
The copilot says it found none, rather than answering from general knowledge.
Fig. 3 — A viewer asks for data their role cannot see. The refusal comes from the tools, not from the prompt, and it names what the viewer can see instead.
Languages

Thai and English, identifiers unchanged.

Questions and answers work in Thai and English. Technical identifiers, such as service names and template text, stay as they are in either language, such as payments-gw.

Is this the payment provider or us?

Most likely the provider. payments-gw has returned 5xx on 31 % of calls since 14:01:58 [1], and its status page reports degraded card authorisation [3]. order-api is healthy on every other dependency [4] and has had no changes in 24 hours [5]. Recommended next step: fail over card payments to the secondary provider.

Every claim cites evidence. Answers respect the asker's role.
ผู้ให้บริการชำระเงินมีปัญหาอยู่ไหม?

มีแนวโน้มสูงว่าปัญหาอยู่ที่ผู้ให้บริการ payments-gw ตอบกลับ 5xx 31 % ของคำขอตั้งแต่ 14:01:58 [1] และหน้าสถานะของผู้ให้บริการแจ้งว่าการอนุมัติบัตรขัดข้อง [3] ส่วน order-api ทำงานปกติกับ dependency อื่นทั้งหมด [4]

Every claim cites evidence. Answers respect the asker’s role.
Fig. 4 — The same question in English and in Thai. Service names, numbers and times stay as they are in either language.
Privacy and roles

Conversations are private and the role is re-checked on every read.

A conversation is private to its user and tenant. Role is checked again on every read and every tool call, not once when a conversation starts, and a downgrade closes restricted history.

Private conversations
A conversation is private to its user and tenant.
Role re-checked
Role is checked again on every read and every tool call, not once when a conversation starts.
Role downgraded
Restricted history from earlier in the conversation is no longer readable.
viewer
Read incidents, service map and dashboards; use the copilot within their access
operator
Acknowledge, resolve and request actions
approver
Approve or reject requested actions
admin
Manage sources, topology, alarms, destinations and the action catalogue
Fig. 5 — A person has one product role in a tenant. Roles are enforced in every query path, API call and copilot tool.
Runbooks

Runbooks are citable knowledge.

Runbooks are written operational guidance for the systems you run, kept in Thai and English. The copilot can read them and cite a passage, with its version, in an answer.

Fail over card payments to the secondary provider

Provider-side fault ranked first with relative confidence 0.81. Runbook RB-PAY-004 applies.

Document
A runbook for one system, kept in Thai and English. The passages are selected in the language of the question.
Revision
Derived from the document’s content, so a changed runbook has a new revision and a citation says which one it relied on.
Reference
Assigned by MonitOps, never taken from model output.
Limit
A passage is prepared guidance. It cannot show that a service is healthy now.
Fig. 6 — A runbook passage cited as the reason a recommended action applies. Opening the citation shows the passage, authorized again at the time of the request.
States

Streaming answers, and an honest unavailable state.

Answers stream as they are written, so text appears while the copilot works. If the model endpoint is unavailable, the copilot says so, and detection, correlation and the computed cause ranking continue.

Streaming

Checking evidence

Most likely the provider. payments-gw has returned 5xx on 31 % of calls since 14:01:58 [1], and its status page reports degraded card authorisation

No evidence found

The copilot says it found none, rather than answering from general knowledge.

Copilot unavailable

The copilot says so. Detection, correlation and the computed cause ranking continue.

Fig. 7 — Answers stream as they are written. When the model endpoint is unavailable, the copilot says so and the rest of MonitOps carries on.
Example questions

Questions operators ask.

The copilot answers questions about incidents, services and logs in Thai or English. The answer changes with the evidence.

Asked inQuestionWhat the copilot does
EnglishIs this payments-gw or us?Compares the incident’s candidates, cites the cause assessment and the evidence, and answers whether the cause is the provider or a service you run.
Thaipayments-gw มีปัญหาอยู่ไหม?Answers in Thai, with the same citations and identifiers unchanged.
ViewerA restricted log attributeRefuses, and offers what the viewer’s role can see.
Fig. 8 — The answer changes with the evidence. When providers are healthy and a single service shows the errors, the answer is that the cause is on your side.
Where to read on

From a question to an approved action.

The copilot never sets a confidence score, a cause class or an approval. Actions run within the authority your team defines, and the articles below describe the copilot in full.

Fig. 9 — The copilot investigates and cites. It never sets a confidence score, a cause class or an approval.

See MonitOps on your own incidents.

We run a working session with your operations team on your services and recent incidents.

Contact salesLog in