Skip to content

Monitoring Tools (o11y)#

The apps/production/o11y directory contains additional observability configurations.

Inactive Status

The files in apps/production/o11y are currently not included in the production kustomization.yaml resource list. These components are defined but not deployed.

Components#

1. API Server SLO (apiserver-slo.yaml)#

  • Kind: PrometheusServiceLevel (Sloth)
  • Objectives:
    • Availability: 99.9% (Errors 5xx/429).
    • Latency: 99% (Requests < 0.4s).
  • Alerts: Generates K8sApiserverAvailabilityAlert and K8sApiserverLatencyAlert.

2. SNMP Probe (snmp-probe.yaml)#

  • Kind: Probe (Prometheus Operator)
  • Module: ubiquiti_unifi
  • Targets: Unifi devices (192.168.1.152, .181, .193).
  • Endpoint: docker.local.isabelsoler.es:9116

3. Uptime Kuma (uptime-kuma.yaml)#

  • Kind: Probe
  • Target: status.local.isabelsoler.es
  • Auth: Uses Basic Auth from uptime-kuma-auth secret.
  • Relabeling: Rewrites monitor_url to mask credentials in PostgreSQL connection strings.

Recommendations#

Activate o11y

If these probes and SLOs are desired, add - ../base/o11y (if a base exists) or direct file references (e.g., - o11y/apiserver-slo.yaml) to apps/production/kustomization.yaml.

Sloth Integration

The root kustomization.yaml installs Sloth CRDs. Enabling apiserver-slo.yaml would leverage this to provide automatic high-quality recording rules and alerts for the Kubernetes API.