Skip to content

Telegram Companion — owner E2E (lab side)

Companion (MacBook archive app) is a thin consumer of LiteLLM, Phoenix, and telemetry. Full owner checklist with Mac steps lives in the Companion repo:

docs/homelab-owner-e2e.md (local: /Users/renjamin/Documents/Projects/TelegramAudioTranscriber/docs/homelab-owner-e2e.md)

This page is the lab-only slice so it sits next to llm-observability.md and monitoring client onboarding.

Lab checklist

# Task Pointer
1 UDM: Servers→Personal allow 192.168.6.17 → Mac IP:11434 Same shape as PC 192.168.3.17 in firewall-policy.md
2 LiteLLM aliases companion-archive-default (+ optional deep / vision) Edit services/litellm/config.yaml; redeploy per LiteLLM README. Vision alias needs ollama pull huihui_ai/qwen2.5-vl-abliterated:7b on the Mac.
3 Virtual key alias telegram-companion Admin UI — llm-observability.md § One-time setup; allow companion-archive-vision if the key is allowlisted
4 TELEMETRY_CLIENTS.telegram_companion + render Same as GHA clients in github-actions-observability.md; sudo scripts/render-monitoring-secrets.sh
5 Optional Prometheus scrape Mac:8000/metrics Static job precedent reddit-explorer in monitoring README
6 Smoke LiteLLM → Phoenix llm-observability.md § E2E Tests using model companion-archive-default; vision smoke uses companion-archive-vision with an image

Do not

  • Invent Tempo exporters (Tempo is not deployed).
  • Point Companion at raw loki:3100 — use https://telemetry.infra.realemail.app.
  • Reuse Alertmanager’s Discord webhook in Companion .env.
  • Collide Loki job=enhanced-tdler (Enhanced TDLer) with job=telegram-companion.