Use case · DevOps & SRE

DigUp for DevOps & SRE

Incidents produce screenshots, Zoom dumps, and PDF postmortems. DigUp ranks them with on-device EmbeddingGemma 2 so you find the graph you saw at 02:00.

On-device flowSchematic: DigUp uses EmbeddingGemma 2 for DevOps and SRE local search
Original schematic — DigUp indexes local files with EmbeddingGemma 2 (llama.cpp).

Sourced snapshot (2026-10-15)

FactValueSource
ModelEmbeddingGemma 2 · ~740M params · ~865 MB Q8 via llama.cppGoogle AI · DigUp README
Vector space768-d shared multimodal spaceGoogle AI · DigUp README
Mac / Win·Linux0.6.1 · 0.7.0-beta.1GitHub Releases
Stars / forks~3,768 / ~254GitHub API

Pain → DigUp workflow → tip

PainDigUp + EmbeddingGemma 2 workflowTip
Postmortem PDF section on rollbackPDF semantic searchOpen at section
Grafana screenshot from last SEVImage embeddings (+ OCR on Mac)Search by panel text/look
Bridge recording timestampAudio/video windowsJump near decision
IaC snippetcode: opt-inOpen at line

Numbered checklist

  1. Install DigUp on the admin workstation you control.
  2. Index Incidents / Runbooks / MetricsExports (local).
  3. Complete EmbeddingGemma 2 (~865 MB); Use Files… if HF blocked (#25).
  4. Enable code search for Terraform/Helm repos.
  5. Prefer overnight indexing; verify GPU on Win/Linux via speed.log.

Why EmbeddingGemma 2 matters here

Google’s EmbeddingGemma 2 (~740M, unified 768-d multimodal space) is what DigUp runs via llama.cpp (~865 MB Q8 package). One query can rank images, PDF pages, audio windows, video frames, and optional code — see the local multimodal guide and model page. digup.run is not Google-official.

Downloads & installs

Related