eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/reference/services/loki.md
Erich Blume 34fceff627 Update Alloy, Prometheus, Loki, Grafana reference cards for flyio-proxy 
Add Fly.io proxy as a third Alloy deployment, document the new
remote_write source in Prometheus, new log source in Loki, and
two new dashboards in Grafana.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-08 10:05:13 -08:00

1.3 KiB
Raw Blame History

title tags
Loki
service
observability

Loki

Log aggregation system for BlumeOps infrastructure.

Quick Reference

Property Value
URL https://loki.ops.eblu.me
Tailscale URL https://loki.tail8d86e.ts.net
Namespace monitoring
Image grafana/loki:3.4.2
Storage 50Gi PVC
Retention 31 days

Architecture

  • Single-node deployment with filesystem storage
  • TSDB index with 24h period
  • Logs collected by alloy and pushed via Loki API
  • Queried via grafana

Log Sources

From Indri (via Alloy):

  • forgejo, tailscale (brew services)
  • alloy, borgmatic, zot, jellyfin (LaunchAgents)

From Kubernetes (via Alloy DaemonSet):

  • All pods in all namespaces

From Fly.io proxy (via embedded Alloy):

  • nginx JSON access logs ({instance="flyio-proxy", job="flyio-nginx"})

Query Examples (LogQL)

{service="forgejo"}                     # All forgejo logs
{service="borgmatic", stream="stderr"}  # Borgmatic errors
{host="indri"} |= "error"               # All logs containing "error"
{instance="flyio-proxy"} |= "docs.eblu.me" # Fly.io proxy access logs for docs

Related