Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Managing services

This section describes how you can reconfigure, restart, and otherwise manage the services running on your system.

Viewing all services

To view the status of all services, in the Admin App, click Services.

For each service, the page shows:

  • The service name
  • The service state:
    • Healthy: The service is running normally.
    • Unconfigured: The service has yet to be configured and deployed.
    • Deploying: The system is currently starting or restarting the service. This can happen when:
      • You move the service to run on a completely different set of instances.
      • You repair a service.
    • Balancing: The service is running normally, but performing some background maintenance operations.
    • Under-protected: In a multi-instance system, one or more of the instances on which a service is configured to run are offline.
    • Failed: The service is not running or the system cannot communicate with the service.
  • CPU Usage: The current percentage CPU usage for the service across all instances on which it's running.
  • Memory: The current RAM usage for the service across all instances on which it's running.
  • Disk Used: The current total amount of disk space that the service is using across all instances on which it's running.

Viewing individual service status

To view the detailed status for an individual service, select the service on the Services page.

In addition to the status information, the page shows:

  • Instances: A list of all instances on which the service is running.
  • Volumes: To view a list of volumes used by the service, select the row for an instance in the Instances section.
  • Network: [Internal|External]: Which network type this service uses to receive communications.

    This section also displays a list of the ports that the service uses.

  • Configuration settings: The settings you can configure for the service.
  • Service Units: The total number of service units currently being spent to run this service. This value is equal to the service's service unit cost times the number of instances on which the service is running.
  • Service unit cost: The number of service units required to run the service on one instance.
  • Service Instance Types: For services that have multiple types, the types that are currently running.
  • Instance Pool: For floating services, the instances that this service is eligible to run on.
  • Events: A list of all system events for the service.

Related CLI commands

getService

listServices

Related REST API methods

GET /services

GET /services/{id}

You can get help on specific REST API methods for the Admin App at REST API - Admin.

 

  • Was this article helpful?