Skip to content

Sources

What Nota knows, it learns from sources: programs and files you already have. You mix them freely. Each reports only its part, and none needs to know of another.

SourceWhat forHow
List (CSV)deadlines, invoices, recurring amounts — everything no system reportsa file or an address; the two templates from nota init
Plana way of working as a template that one start date makes concretetemplates/plans/app-development.csv
todo.txt / Taskwarriortasks with a due datethe file you already keep
Beancountcost, revenue and open receivables from the ledger"format": "beancount"
Checks from outsidereachability, ports, certificate expirychecks in the probe
This machinedisk, memory, load, a sign of life"host" in the probe; nota init writes it
Hetzner Cloudservers, volumes, IPs with list priceshetzner in the probe, with a read-only token
Agent with Vectorthe same as “this machine” and more, for those who run Vector anyway; runs of jobsthe agent/ folder of the source: the package nota-agent, with nota-report for jobs
Grafana / Alertmanageralerts that already existthe template templates/vector/grafana-alerts.yaml
Your own programseverything else, such as the steps of an AI processone HTTP call to /v1/ingest
Configurationthings and prices you set by handconf.d/*.json on the server

A source reports. Nota evaluates. Things are ticked off where they live: the payment is booked in the ledger, the task gets its x in todo.txt, the row in the list gets a date.

The probe reads files and asks addresses. It starts no other programs. A Taskwarrior export, for example, is written by your own cron job.