Vultr DocsLatest Content


How to Monitor Vultr Managed Database for Valkey

Updated on 11 September, 2025

Learn how to monitor your Vultr Managed Database for Valkey instance to ensure optimal performance and availability.


Monitoring Vultr Managed Database for Valkey allows you to view monthly charges, vCPU, memory, and disk usage. Checking your managed database stats provides insight that can help you scale your database, detect performance issues, establish robust backup schedules, and more.

Follow this guide to monitor Vultr Managed Database for Valkey using Vultr Customer Portal, API, and CLI.

Vultr Customer Portal

  • Vultr Customer Portal
  • Vultr API
  • Vultr CLI
  1. Navigate to Products and select Databases.
  2. Click the target database instance.
  3. View the database instance summary.
  4. Click Usage Graphs to view vCPU usage.
  5. View the Network usage.
  1. List all the database instances by sending a GET request to the List Managed Databases endpoint and note the database ID. For example, 43b4c774-5dff-4ac0-a01f-78a23c2205b5.

    console
    $ curl "https://api.vultr.com/v2/databases" \
        -X GET \
        -H "Authorization: Bearer ${VULTR_API_KEY}"
    
  2. Send a GET request to the Get Database Usage Information endpoint and specify the database ID to retrieve the database instance usage information. The information includes disk, memory, and vCPU usage.

    console
    $ curl "https://api.vultr.com/v2/databases/database_id/usage" \
        -X GET \
        -H "Authorization: Bearer ${VULTR_API_KEY}"
    

    Visit the Get Database Usage Information endpoint to view additional attributes to add to your request.

  1. List all database instances and note the database ID. For instance, d6ac2a3c-92ea-43ef-8185-71a23e58ad8c.

    console
    $ vultr-cli database list --summarize
    
  2. List the database usage information by specifying a database ID.

    console
    $ vultr-cli database usage get database_id
    

    Run vultr-cli database usage --help to view all options.

Comments

No comments yet.