loki

Loki does not have an HTTPRoute on the internal ingress gateway, so it requires port-forward access (unlike Prometheus and Grafana which are available via DNS).

Why port-forward? Loki's gateway component is disabled (replicas: 0) and no HTTPRoute exists for it on the internal ingress gateway. For other services that do have HTTPRoutes (Prometheus, Grafana, Alertmanager), prefer using the internal DNS URLs instead -- see the k8s skill for the full URL table.

For homelab-specific LogQL queries (Flux, Cilium, CloudNative-PG, etc.), see references/queries.md.

Query Loki API for cluster logs and debugging. Use when investigating application errors, searching logs, debugging pod issues, or querying log patterns. Use when: (1) Searching logs for errors or patterns, (2) Investigating pod or service issues via logs, (3) Querying Kubernetes events, (4) Debugging Flux reconciliation or platform service failures, (5) Running LogQL queries, (6) Checking log rates or volumes. Triggers: "check logs", "search logs", "query loki", "logql", "show me logs", "what happened in", "log errors", "find in logs", "tail logs", "kubernetes events", "recent logs", "log query", "debug logs" Source: ionfury/homelab.