Cloud Audit
Cloud Hosted audit is available inside the customer controller. You do not need a local worker UI for Cloud Hosted runs.
Open:
https://controller.mergeloom.aiThen go to Audit.
Audit Tabs
Section titled “Audit Tabs”Cloud Hosted Audit contains these main views where your plan enables them.
| Tab | Use it for |
|---|---|
| Ticket Audit | Run outcomes, stage timeline, ticket, repository, assignee, input tokens, output tokens, cost estimate, duration, and review links. |
| Code Audit | Repository-level and file-level line evidence for code written through MergeLoom. |
| Context Engine Audit | Indexing, context-pack, and context-source visibility where Context Engine is enabled. |
| Controller Audit | Intake, queue, routing, integration, assignment, and workflow state events. |
Live Run State
Section titled “Live Run State”The current cloud run appears on the Cloud Runtime page. Use it when you want to see whether a managed executor is actively working.
The Audit page is for completed or recorded activity. The Cloud Runtime page is for the current execution state.
Cloud Runtime and Cloud Audit data can be shown from recently refreshed controller views. If a run has just started or just finished, recheck after the next refresh before assuming audit evidence is missing.
Token and Cost Data
Section titled “Token and Cost Data”Cloud Hosted ticket audit records:
- input token count
- output token count
- approximate cloud provider cost for the run
- duration
- model used
This is used for workspace metrics, billing visibility, and cost-per-review reporting.
What Cloud Audit Does Not Replace
Section titled “What Cloud Audit Does Not Replace”Cloud Hosted audit does not remove human review. It gives the reviewer enough evidence to understand what happened before the PR or MR was opened.
Use the code host as the approval system. Use MergeLoom audit to inspect the automation path that produced the review request.
If a Cloud Run Is Missing from Audit
Section titled “If a Cloud Run Is Missing from Audit”Check:
- the ticket matched intake
- the ticket was assigned to a workspace user if required
- the repository routing label matched Repository catalog
- the workspace had cloud runtime ready
- email verification and card verification were complete if required
- AI credits were available
- the provider did not fail before usage could be recorded
Controller Audit should show intake and queue issues even when the worker did not complete the job.