How to Monitor a MicroVM

Last verified 17 Nov 2026

DigitalOcean MicroVMs are lightweight virtual machines that run a container image in an isolated kernel, pause automatically when idle, and resume on the next request with memory, files, and processes intact.

You can view a DigitalOcean MicroVM’s state and URL with the Control Panel, doctl, or the API. For what each state means, see MicroVM Lifecycle.

MicroVMs also send telemetry to DigitalOcean Insights:

  • Metrics: Usage and lifecycle timing, such as vCPU and memory usage and startup time. Insights stores metrics for every MicroVM.
  • Platform logs: A log line for each lifecycle event, such as when the MicroVM is created, paused, or resumed. Off by default.
  • Platform traces: A trace for each create, pause, resume, and destroy operation, with a span for each step. Off by default.

Logs and traces describe what the platform does to the MicroVM. They do not include your application’s own logs or traces. Logs and traces count toward your Insights ingestion usage. For rates, see Insights Pricing.

Monitor a MicroVM Using the Control Panel

Go to the MicroVMs page. The list shows each MicroVM’s name, status, and tags. To find a MicroVM, use Search by MicroVM name.

Click a MicroVM’s name to open its details page, which has Overview, Checkpoints, Console, Insights, and Settings tabs.

The Overview tab shows the following:

  • Header: The MicroVM’s status, region, size, and image.
  • Endpoint: The MicroVM’s default URL, after provisioning finishes.
  • Configuration details: The size, region, networking, HTTP port and protocol, environment variables, and image. For a MicroVM created from a checkpoint, Restored from shows the checkpoint.
  • Lifecycle: The current state, the failure reason if the MicroVM failed, and the resource ID.
  • Auto-pause and Auto-resume: Whether each is on, and the idle timeout.
  • Outbound network: Whether outbound traffic is restricted, and the allowed destinations.

View Metrics

Click the Insights tab to see the MicroVM’s metrics. The tab has two sections:

  • Usage: Active Time, Active vs Paused Time, vCPU Usage, Memory Usage, Network Usage, and Storage Usage. Storage usage includes the MicroVM’s disk and its checkpoints.
  • Lifecycle: Cold Startup Time and Warm Startup Time, which measure how long the MicroVM takes to become active from a create or cold resume and from a warm or checkpoint start, plus Pause Time and Time to Pause.

You can also query MicroVM metrics in Insights. Metric names start with do.microvms., such as do.microvms.vcpu_usage, and the resource is do:microvm:<your-microvm-id>. See How to Explore and Query Metrics.

Turn Logs and Traces On or Off

Choose whether Insights stores platform logs and traces when you create the MicroVM. To change the choice later, click the MicroVM’s Settings tab, then click Edit in the Insights row. The row shows Metrics Enabled, Logs Enabled, and Traces Enabled for each signal Insights stores. To change telemetry settings for your whole team, click Insights settings.

View Logs and Traces

To view a MicroVM’s logs and traces, go to Insights and filter by the service name microvms. See How to View Logs and How to View Traces.

Platform logs include the following messages:

  • MicroVM created and running.
  • MicroVM paused.
  • MicroVM resumed and running.

Each platform trace has a root span named for the operation, such as microvm.create, microvm.pause, microvm.resume, or microvm.destroy. Its child spans show the steps of the operation, such as workload.start, ingress.create, and ready for a create, so you can see which step took the most time.

Monitor a MicroVM Using doctl

Show the MicroVM’s state and URL.

How to Retrieve Information About a MicroVM Using the DigitalOcean CLI
  1. Install doctl, the official DigitalOcean CLI.
  2. Create a personal access token and save it for use with doctl.
  3. Use the token to grant doctl access to your DigitalOcean account.
    doctl auth init
  4. Finally, run doctl compute microvm get. Basic usage looks like this, but you can read the usage docs for more details:
    doctl compute microvm get <microvm-id> [flags]

To list all of your MicroVMs, run doctl compute microvm list. You can filter the list with --region, --name, and --tag-name. Filters combine with AND. --name matches any MicroVM whose name contains the value, ignoring case.

Monitor a MicroVM Using the API

Send a GET request to /v2/microvms/<your-microvm-id>. The response returns the state in state and the URLs in urls. If the state is failed, failure_reason explains why.

How to Retrieve a MicroVM Using the DigitalOcean API

Create a personal access token and save it for use with the API.

cURL

Send a GET request to https://api.digitalocean.com/v2/microvms/{microvm_id}.

Using cURL:

curl -X GET \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
  "https://api.digitalocean.com/v2/microvms/01a0ef1a-d873-793d-ae6a-5dd6239be62a"

To list all of your MicroVMs, send a GET request to /v2/microvms. You can filter the list with the region, name, and tag_name query parameters. name matches any MicroVM whose name contains the value, ignoring case.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.