DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to put a live metric chart beside its explanation with Oxynote

Build one page where a Prometheus or SQL chart sits next to the text that explains it.

Credentials. SQL queries need a database connection, so use a read-only account and never paste production passwords into a shared page.

Who it is forAn on-call engineer or service owner who keeps explaining Grafana panels in a separate doc and wants chart and explanation to stay in sync.

The problemGrafana descriptions are short tooltips, and a separate Notion doc drifts from the chart it describes.

The outcomeA page with a Live Metrics block that runs its own query and an explanation written under it, reviewable as one unit.

What you need first

  • Docker installed, with port 8080 free on the host
  • A Prometheus server or a PostgreSQL, MySQL or MariaDB database to query for live metric blocks
  • The default login from the README ([email protected]) changed before any real data goes in
  • For agent access: Claude Code or Codex installed, able to use MCP over OAuth

Steps

  1. Run docker run -d --name oxynote -p 8080:8080 -v oxynote_data:/oxynote/data ghcr.io/oxynote/oxynote:latest (join the lines into one command). (inferred, check the README)
  2. Open http://localhost:8080 and log in with [email protected] and oxynote-admin-1234, then change that password.
  3. Create a new page and insert a Live Metrics block. (inferred, check the README)
  4. Add a Prometheus or SQL query to the block and choose time series, bar chart or gauge. (inferred, check the README)
  5. Type the explanation of what the chart shows and what to do when it crosses the threshold, directly under the block.

Prompt for your agent

Using the oxynote/oxynote repo running at <oxynote-url>, create a page titled <page-title> with a Live Metrics block that runs <prometheus-or-sql-query> and an explanation paragraph under it. Expected output: the page URL and a list of the blocks on it. Verify that the chart renders with live data and that the explanation is on the same page.

Caveat. The README does not describe the exact steps for adding a query in the UI, so check the current screens against the docs before relying on these steps.

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