Skip to main content


Service in co.brick observe represents a functional object in the system. In Kubernetes context the closest abstraction is a Workload.

To determine health status of a Service in a Kubernetes system, co.brick observe performs a series of checks on the following Kubernetes objects:

  • Workloads:
    • Pods,
    • Deployments,
    • DaemonSets,
    • StatefulSets,
  • Storage:
    • PersistentVolumes,
    • PersistentVolumeClaims.

These checks have been chosen to strike a balance between the number of checks and their performance, providing a comprehensive overview of the system's health while avoiding false positives. The Services View presents the current health status of each service, along with the duration of time it has remained in that state.

Health status of a services