Metrics

Some questions get asked every week in the same words: the biggest recurring spend, which merchant did the most transactions yesterday, how many tickets came in overnight. Each answer is a figure that is true for a moment and then stale, and nobody keeps the series.

Metrics turn such a question into something Memtro measures on a schedule. A metric is a name, the question in your words, and a recipe: a read-only SQL query against one of your database connections, or any connector's read tool with a path to the number in its answer. Every measurement is kept as a point for the chart and written to memory as a fact with its provenance, so "what was it in July" and "how has it moved since the price change" are ordinary questions, and the figure sits beside everything else Memtro knows rather than in a dashboard of its own.

Metrics are a feature an administrator turns on under Organisation → General → Features, off for a new organisation like the other registers: until it is on the tab is not shown, the assistant is not offered the metric tools, and nothing is measured.

Saving one

• From chat. Ask something the assistant answers with a query, then say "save that as a metric called daily transactions, measured every morning". The assistant calls memtro_save_metric with the query and connection it just used, or the tool and the path to the number, measures once to prove the recipe yields one figure, and refuses to save if it does not.
• By hand. Memory → Metrics → New metric: name, question, unit, then either a database connection and a SQL query or a connector tool with its input and a path, a schedule (presets or a cron line) and a timezone. It is measured once with your own connections and grants before it is saved.

Saving, changing and deleting metrics needs Keep metrics, a permission every member holds until the organisation decides otherwise.

How it runs

On its schedule, daily at six by default, Memtro measures each metric as the person who saved it: their connections, their grants, their routing. The recipe must yield exactly one number; an empty result or a row with several numbers is recorded as a failure on the page rather than measured as the wrong thing. Each run writes a point and a memory, "Daily transactions was 1,234 on 16 October 2026", of kind fact, dated to the day, naming the tool and the metric as its source, and the metric itself is an entity in the graph. Deleting a metric removes it and its points; the memories it wrote stay, because they were true.

Reading them

The Metrics tab under Memory shows each metric with its latest figure, a sparkline of recent measurements, the next run and the last error. Run now measures it as you; Pause stops the schedule and Resume books it from now. In chat, memtro_metrics lists them with recent values, which is also how the assistant checks whether a question is already being measured before it saves another.

What it does not do

• One number per measurement. A query that returns a table is not a metric; save a figure from it.
• Reading only. A recipe that would change something in a connected system is refused.
• It runs as a person. If the person who saved a metric leaves the organisation, their metrics stop until somebody saves them again.