Metrics

Metrics provides near real-time information about vCPU and Memory that your service uses. This information is valuable as you will be able to optimize your cost by viewing your actual usage compared to what you are paying for. In addition to cost savings, you may also detect issues with your service by seeing how many times it has restarted. A Restart is when your service has crashed and KintoHub has automatically brought it back online.

View Metrics#

  1. Choose your environment you are interested in deploying into at the top left.
  2. Create any service or select a previous service you have made.
  3. By default, you will be placed on the Overview tab.

Metrics Information#

Summary#

Shows the total amount of resources that your entire service is taking up.

  • Memory - The total memory and memory usage our service is using.
  • vCPU - The total vCPU and vCPU usage your service is using
    • When vCPU is shared, the value will be shown as SHARED and you will not be able to monitor usage.

Summary

Instances#

Instances are individual live and running apps that make up your service.

  • Name/Instance - The unique name and instance identifier.
  • vCPU - Usage and dedicated vCPU allocated to your instance.
    • When vCPU is shared, the value will be shown as SHARED and you will not be able to monitor usage.
  • Memory - Usage and dedicated memory allocated to your instance.
  • Restarts - Number of times your service has crashed and recovered.
  • Status - The health of your instance.
    • Healthy - Readily available to serve traffic
    • Unhealthy - Currently not available and is either starting up or has crashed
    • Completed - Service has been terminated due to a Deploy or Restart action
  • Actions - ... Provides actions you can execute on your instance
    • Restart Instance - If there is an issue, you can force an instance restart
    • View Console - Takes you to your Console tab and filters the logs with the instance you specified

Instance