Service usage

The Service usage page provides a list of all services that are associated with the runtime in a tabular format.

The service graphs show the top performing services that are sorted by response time and the request counts in descending order. Metrics on the Service usage page include services at all levels.

The Service usage page shows the following graphs:

  • Top 5 slow Services by response time - The top five services that have the longest average response time over the time range (excludes system services).
  • Top 5 services by request count - The top five services that have the most request count over the time range (excludes system services).

The Service usage page also shows the following data that is related to Service instances, Cache and prefetch information, and Circuit breaker information:

  • Search - Filter the content of the table in the Service usage page using the Search option. It also provides options to exclude system services and services that are not running currently from the view.
  • Settings - Set the table display settings as one of the following values:

    • Enable Zebra stripes if you want to display alternative rows with different background colors.

    • Select which columns you want to display in the table using the Show Columns menu option.

  • Reset server cache - Resets the runtime cache to clear the count and restart the data collection timers for all services.

Service instances

The Service instances tab displays information about all past and current running services. The data is for all instances in the same environment.

  • Package - Package that contains the service.
    Note: The Package column is not displayed by default. Click Show Columns to view this column.
  • Name - Full qualified name of the service that is running or has run.
  • Available threads - Threads that are running.
  • Running services - Number of instances of the service that is running.
  • Count - Number of instances of this service that ran in the specified time.
  • Success - Number of successful runs of the service.
  • Failure - Number of runs of this service that ended in failure.
  • Last ran - Date and time the service is last run.
  • Response time (ms) - Average time of all responses within a given sampling interval, such as 60 seconds.
    • Minimum - Minimum time, in milliseconds, that the service took to run in the selected period.
    • Average - Average time, in milliseconds, that the service took to run in the selected period.
    • Maximum - Maximum time, in milliseconds, that the service took to run in the selected period.
  • Cache, prefetch, circuit breaker - Indicates whether the service’s caching option or prefetch option is enabled, or whether the service is a circuit breaker. So, one or more icons are displayed as follows:
    • : Indicates that Cache is enabled.
    • : Indicates Prefetch is enabled.
    • : Indicates that the service is a Circuit Breaker.

Cache and Prefetch Information

The Cache and prefetch information tab displays cache utilization information for only those services that are using cache.

The Cache and prefetch information tab displays the following information:

  • Package - Package that contains the service.
    Note: This column is not displayed by default. Click Show Columns to view this column.
  • Name - Full qualified name of the service that is running or has run.
  • Last cache hit - Date and time that a cached result for this service was last accessed.
  • Cache hits - Total number of times that a cached result for this service has been accessed.
  • Cache hits/Total count - Percentage of requests for this service that have been fulfilled by retrieving the results from cache.
  • Cache entries - Number of active cache entries for the service.
  • Cache expires - Time when the cache expires for the service.
  • Last prefetch - Date and time that the runtime is last prefetched and cached the results for the service.
    Note: The cache may not be refreshed at the exact time that is specified in Cache expires. It can vary from zero to 15 seconds, according to the cache sweeper thread.
  • Total prefetches - Total number of times the runtime has prefetched and cached the results for the service in the last poll interval (the poll interval is set to 10 minutes on most servers).
  • Recent prefetch - Total number of times the runtime has prefetched and cached the results for the service in the last poll interval (the poll interval is set to 10 minutes on most servers).

Circuit Breaker Information

The Circuit breaker information tab displays circuit breaker statistics for each service with a configured circuit breaker. Runtimes gather the circuit breaker statistics.

The circuit breaker feature is available by default for a service that resides on a Microservices Runtime instance. To use the circuit breaker feature with runtimes, you must have additional licensing.

If a circuit breaker is not configured for any service, the Circuit breaker information table displays the message No Services with a circuit breaker enabled.

The Circuit breaker information tab displays the following information:

  • Package - Package that contains the service.
    Note: This column is not displayed by default. Click Show Columns to view this column.
  • Name - Full qualified name of the service that is running or has run.
  • State - State of the circuit can be one of the following:
    • Closed - Service runs.
    • Open - Service does not execute. Instead, depending on the circuit breaker configuration, the service returns an exception or runs an alternative service.
    • Half-open - First request for this service since the circuit state changes to half-open results in service execution. All other requests await. If the service runs successfully, the circuit is closed, and the waiting requests run. If the service ends with a failure exception, the circuit is re-opened.
    • Open time - Time when circuit was opened.
  • Open time - Time when an action was performed to close the circuit, that is, to retry the execute call.
  • Half-open time - Time when the execution of the actual service attempts was made. If successful, the circuit is Closed; if unsuccessful, the circuit is Opened.
  • Closed time - Time when the circuit was last closed. Time here represents the last successful execution of the service.
  • Open count - Number of times the circuit was opened since the runtime started.
  • Request count - Number of incoming requests since the circuit was last opened.