whatisgithub

What is ai_monitoring?

tarrinho/ai_monitoring — explained in plain English

Analysis updated 2026-05-18

16PythonAudience · ops devopsComplexity · 3/5LicenseSetup · moderate

In one sentence

A self-hosted dashboard that tracks how much you are spending on your own AI models, plus the health of the servers and GPUs running them.

Mindmap

mindmap
  root((AI-Monitoring))
    What it does
      Tracks LLM spend
      Tracks token usage
      Watches GPU health
      Watches container health
    Tech stack
      Python
      aiohttp
      SQLite
      Docker
    Use cases
      Budget tracking
      Spend alerts
      Infra health checks
      Cost reporting
    Audience
      Self-hosted AI operators
      Small teams
      Homelab builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Track how much money you are spending across every API key on a self-hosted LLM setup.

USE CASE 2

Watch GPU, host, and container health for Ollama, llama.cpp, and vLLM backends in one place.

USE CASE 3

Get alerted by webhook when spending spikes or a budget is close to its cap.

USE CASE 4

Export usage and cost history to CSV for reporting to a team or manager.

What is it built with?

PythonaiohttpSQLiteDockerLiteLLM

How does it compare?

tarrinho/ai_monitoring920linjerry-stack/capital-studioadya84/ha-world-cup-2026
Stars161616
LanguagePythonPythonPython
Setup difficultymoderateeasyeasy
Complexity3/53/52/5
Audienceops devopsresearchergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Needs Docker and a running LiteLLM/Ollama/llama.cpp/vLLM backend to see LLM-specific dashboards.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

So what is it?

AI-Monitoring is a self-hosted dashboard for keeping an eye on the cost and health of a homegrown AI system built around large language models. If you are running your own AI models instead of paying for a service like OpenAI, this tool watches how much you are spending, how much data is flowing through your models, and whether the computers and software running everything are healthy. It works with a piece of software called LiteLLM to track spending and usage per API key, and it also checks on GPU, host machine, and container health for tools like Ollama, llama.cpp, and vLLM. Everything runs from one small application, and it checks each system's own built in reporting instead of adding extra monitoring software on top. The main dashboard, called Spend and Quota, puts money and usage front and center. It shows total real world cash spent on external paid models next to an estimate for self-hosted costs, daily and monthly usage charts, cost broken down by each individual key or by team, and a list of budgets ranked by how close each one is to running out. Beyond spending, there are ten different dashboard views covering an overview, LiteLLM, GPU, Ollama, llama.cpp, vLLM, network activity, alerts, spend and quota, and settings. The interface has a collapsible sidebar, a day and night viewing mode, adjustable time windows, and the ability to export data to CSV. Data is stored for up to a year by default, with detailed recent data and coarser summaries for older history. The tool can send alerts when spending spikes or when unusual activity is detected, including webhook notifications and a way to test that alerts work. It is built to run safely, using a minimal Alpine Linux base, running as a non-root user, and supporting multiple computer architectures. Getting started involves copying an example settings file, filling in a few details, and starting it with Docker. It works even without any backend configured, showing basic host statistics until you connect it to your AI setup. It is released under the Apache 2.0 license. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Help me set up AI-Monitoring with Docker Compose to watch my LiteLLM spending.
Prompt 2
Show me how to configure per-key budgets and alerts in AI-Monitoring.
Prompt 3
Explain how AI-Monitoring separates real cash spend from estimated self-hosted cost.
Prompt 4
Help me verify the AI-Monitoring container image signature with cosign before deploying it.

Frequently asked questions

What is ai_monitoring?

A self-hosted dashboard that tracks how much you are spending on your own AI models, plus the health of the servers and GPUs running them.

What language is ai_monitoring written in?

Mainly Python. The stack also includes Python, aiohttp, SQLite.

What license does ai_monitoring use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is ai_monitoring to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is ai_monitoring for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.