Create a Grafana Dashboard for Backstage Metrics on Mimir (OTel → Alloy → Mimir)
This post continues from: Backstage metrics flow: Backstage (OpenTelemetry SDK) → OTLP/HTTP → Alloy → remote_write → Mimir → Grafana […]
This post continues from: Backstage metrics flow: Backstage (OpenTelemetry SDK) → OTLP/HTTP → Alloy → remote_write → Mimir → Grafana […]
This post migrates Backstage backend monitoring from kube-prometheus-stack (ServiceMonitor + Prometheus scrape) to an LGTM-style push pipeline: Backstage (OpenTelemetry SDK)
This post installs Grafana Alloy on Kubernetes as a push-only OpenTelemetry gateway and exposes: We keep OTLP/gRPC (4317) enabled inside
This post installs Grafana Mimir (metrics backend) on Kubernetes, using Ceph RGW (S3-compatible) for long-term object storage. Why Mimir first
This post adds OpenTelemetry metrics to your Backstage backend and makes them scrapable by Prometheus Operator (kube-prometheus-stack) via a ServiceMonitor.
Metrics Server collects CPU / memory usage from each node’s Kubelet and exposes it via the Kubernetes Metrics API. This
If you run Metrics Server (or anything that connects to the Kubelet HTTPS endpoint on 10250), you may see TLS
This post shows how to deploy the official Zabbix Kubernetes Helm chart into your cluster, run a Zabbix Proxy inside
Zabbix 7.4 includes AWS by HTTP templates. You create a single account host (e.g., aws-prod) and link only the base
TL;DR Install the OPNsense Zabbix Agent plugin → enable it → set Hostname to exactly your Zabbix host name →