Skip to content
Stackship documentation Svenska

Monitoring

What the platform measures about your resources, where you see it, and how alerts tell you that something needs attention.

  • Alerts — How the platform decides to raise an alert on a resource, how an open alert changes and resolves, what its level means, and how long alerts are kept.
  • Alert rules — Every built-in rule that raises an alert on a resource, the level it raises, when it fires and when it resolves, and the details each alert carries.
  • View alerts — See a resource's firing and resolved alerts in the portal, list the alerts firing across a boundary with the CLI, and read them through the API.
  • API reference — Every HTTP endpoint of the monitoring module: authentication, IAM action, parameters, bodies and status codes.
  • What monitoring needs from the cluster — How the Monitoring module finds the kubelets, the ingress controller and Longhorn, what each gives, what is missing without them, and the settings that point it at them.
  • Configuration reference — Configuration keys of the monitoring module: sections, environment variables, types and defaults.
  • The Health page — What the Health page's Map, Nodes and Database tabs show about the platform's components, its nodes' capacity and its own database, and who can open each.
  • Monitoring — What the platform measures about your resources, where you see it, and how alerts tell you that something needs attention.
  • Charts and metrics — Which charts each resource type shows, what every chart measures and in which unit, and the series the platform stores for a resource.
  • Metrics — Where a resource's metrics come from, how a reading is filed under its resource, what the percentages are measured against, and how long the history is kept.
  • Read a resource's metrics — Find a resource's CPU, memory, disk, network and HTTP charts in the portal, read the notes under them, and fetch the same numbers through the API.
  • Permissions — The actions that govern metrics, alerts and the Health page, the scope each is checked at, and the roles that hold them.
  • Platform alerts — The alerts about the platform itself — storage, monitoring and conditions other platform components report — where they show, how they leave the cluster, and why no alert email arrives.
  • Metric storage and retention — Where the Monitoring module stores metrics and alerts, how often it collects and checks, how long each tier of metrics and each resolved alert is kept, and how to see that retention is working.
  • Troubleshoot monitoring — Find out why charts are empty for every resource, why HTTP charts see no requests, why storage figures are missing or wrong, and why the monitoring tables keep growing.