DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to scrape server metrics from a local model host with Kyojin

Expose Kyojin's Prometheus metrics endpoint so a monitoring stack can track a local model server.

Authorization notice. Kyojin is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA homelab or small ops owner who runs the model server on a mini PC and wants its health and load in an existing dashboard.

The problemA local model server gives no visibility into load or throughput unless something collects its numbers.

The outcomeA Prometheus setup that reads the server's /metrics endpoint on port 8000.

What you need first

  • AMD Ryzen AI Max+ 395 mini PC with 128 GB of memory (Strix Halo, gfx1151)
  • ROCm build of torch, installed per doc/install.md
  • Python and the hf command-line tool to download model packs
  • Roughly 100 GB of free disk space for a model pack (Qwen pack is 95 GB)

Steps

  1. Start the server per doc/models.md, for example with python tools/qwen/serve.py --model ./qwen-pack --port 8000 -c 131072.
  2. Check that the endpoint responds at /metrics on the host.
  3. Add a Prometheus scrape job that targets the host on port 8000 at path /metrics. (inferred, check the README)
  4. Open the Prometheus UI and confirm the target shows as up. (inferred, check the README)

Prompt for your agent

In the Yamz-Labs/kyojin repo, start the Qwen server on port 8000 and confirm the Prometheus /metrics endpoint responds on <target host>. Expected output: a plain text metrics page from the server. Verify that the response contains metric lines before adding it as a scrape target.

Caveat. The README credits the /metrics endpoint as merged for GLM and MiMo, so confirm it is available for the model you run before building dashboards.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page