Alerts, audit and costs

These five topics cover the installation as a whole, rather than one cluster or one application.

Alerts

The dashboard bell and the administrators’ email always receive the installation’s critical alerts. flui alerts adds other places, and decides whether administrators also hear about warnings. The alerts of one application are on flui app alerts.

flui alerts destination add

Sends alerts to an email address or to a signed webhook.

flui alerts destination add --email oncall@example.com
flui alerts destination add --webhook https://hooks.example.com/flui --min-severity warning
flui alerts destination add --email oncall@example.com --scope all

Flag	Default	Effect
--email <address>	none	Send alerts to this address.
--webhook <url>	none	A public https address that receives a signed JSON POST for every alert. Its host has to resolve, or the destination is refused.
--min-severity <level>	critical	The least severe alert it receives: warning or critical.
--scope <scope>	infrastructure	infrastructure: alerts no application owns (nodes, disks, certificates, platform backups). all: every application’s alerts too, which needs the right to reach application data.
-o, --output <format>	text	text or json.

The command prints the new destination’s id.

flui alerts destination list / test / remove

flui alerts destination list
flui alerts destination test <id>
flui alerts destination remove <id>

list shows each destination with its severity, scope and whether anything has been delivered to it yet. test sends a real test alert, named FluiTestAlert, and says whether it arrived. remove stops sending there.

flui alerts warnings

flui alerts warnings          # what is set
flui alerts warnings --on     # email administrators warnings too
flui alerts warnings --off    # critical alerts only (the default)

Covers warnings about nodes, disks and certificates.

flui audit list

Who did what on this installation, newest first: every change, every refusal, and every read of application data.

flui audit list
flui audit list --user support@example.com --since 7d
flui audit list --data
flui audit list --refused --since 24h

Flag	Default	Effect
--user <email>	none	Only what this person did.
--since <when>	none	From this far back (30m, 8h, 7d) or from a date.
--data	off	Only actions that reached application data.
--refused	off	Only what was refused.
--limit <n>	50	How many records.
-o, --output <format>	text	text or json.

Actions the platform takes on its own are listed too, as platform (system). A short-lived SSH certificate issued to reach a node is one example.

flui costs

What your clusters cost: spent and forecast, month by month and provider by provider, deleted clusters included.

flui costs
flui costs --months 12
flui costs --provider hetzner
flui costs --json

Flag	Default	Effect
--months <n>	6	Calendar months to show, ending with the current one (1 to 24).
--provider <name>	none	Only this provider.
--json	off	Machine-readable output.

Amounts are in euros. For each provider the output says how it bills and whether VAT is included, and breaks the current month down by cluster. Costs are the machines and volumes of your clusters; applications cost nothing on their own. Traffic above what each machine includes is not counted, and the forecast assumes what runs now keeps running until the end of the month. A machine that started before Flui kept the price it was bought at is priced at today’s list price, and the output says how many.

flui inference usage

What the assistant and the console copilots have spent, by model and by person.

flui inference usage
flui inference usage --days 1
flui inference usage --days 0 --price 0.20

Flag	Default	Effect
--days <n>	7	The window to report on. 0 means everything.
--price <amount>	none	Your price per million tokens, to turn the totals into money. Model prices differ, so you supply the number.
--json	off	Machine-readable output.

Showcase

The showcase is the short list of applications this installation puts in front of other people.

flui showcase list
flui showcase add <app> --note "Measures our website. Real visitors."
flui showcase remove <app>

<app> is the application’s slug, name or id. For an app that came with a catalog bundle, use the component’s slug, as flui app list shows it. --note is the line shown next to it. It is stored as the application’s description, so it stays after remove. remove takes the application out of the showcase and leaves it running. All three take --json.