diff --git a/maintenance-ops/compacting-buckets.mdx b/maintenance-ops/compacting-buckets.mdx
index ee896790..4d8b8090 100644
--- a/maintenance-ops/compacting-buckets.mdx
+++ b/maintenance-ops/compacting-buckets.mdx
@@ -16,6 +16,8 @@ You can manually trigger compacting from the [PowerSync Dashboard](https://dashb
 - **Dashboard**: Select your project and instance, go to the **Settings** view, and click the **Compact** button in the "Compact operation history" section.
 - **CLI**: Run `powersync compact` against a linked Cloud instance. The CLI polls until the operation completes, with a default timeout of 30 minutes. Pass `--timeout=<minutes>` to override, or `--timeout=0` to wait indefinitely.
 
+When using PowerSync Cloud, compact logs are available in the Dashboard's **Logs** view. See [Instance Logs](/maintenance-ops/monitoring-and-alerting#instance-logs).
+
 [Defragmenting](/maintenance-ops/compacting-buckets#defragmenting) may still be required.
 
 ### Self-Hosted PowerSync
diff --git a/maintenance-ops/monitoring-and-alerting.mdx b/maintenance-ops/monitoring-and-alerting.mdx
index 118ed91f..d3e2bdfe 100644
--- a/maintenance-ops/monitoring-and-alerting.mdx
+++ b/maintenance-ops/monitoring-and-alerting.mdx
@@ -72,12 +72,16 @@ You have following options:
 
 ## Instance Logs
 
-You can review logs for your PowerSync instance(s) to troubleshoot replication or sync service issues. Logs capture activity from the PowerSync Service and Replicator processes.
+You can review logs for your PowerSync instance(s) to troubleshoot replication or sync service issues. Logs capture activity from the PowerSync Service and Replicator processes, as well as the jobs that run alongside them.
 
 * **Sync & API logs**: Reflect sync processes from the PowerSync Service to clients.
 
 * **Replicator logs**: Reflect replication activity from your source database to the PowerSync Service.
 
+* **Compact logs**: Reflect the [compacting](/maintenance-ops/compacting-buckets) jobs that keep your instance's sync buckets efficient, including the daily automatic job and any manually triggered runs.
+
+* **Migration logs**: Reflect the migration job that prepares your instance's storage during a deploy. Check these if a deploy fails at that step.
+
 <Note>
   **Availability**
 
@@ -104,7 +108,7 @@ Access instance logs through the [PowerSync Dashboard](https://dashboard.powersy
 
 You can manage logs with the following options:
 
-* **Log Type**: Switch between **Sync & API logs** (from the PowerSync Service API container, which handles streaming sync connections as well as other API calls) and **Replication logs**.
+* **Log Type**: Switch between **Sync & API logs** (from the PowerSync Service API container, which handles streaming sync connections as well as other API calls), **Replication logs**, **Compact logs**, and **Migration logs**.
 * **Log Levels**: Show or hide `Info`, `Error`, `Warn`, and `Debug` entries.
 * **Time Range**: Limit results to a relative window (last 15 minutes, last hour, etc.) or a custom range. The available window depends on your plan's retention period. You can also click the timestamp on any log entry to set it as the start or end of the time range.
 * **Sort Order**: Sort by newest or oldest first.