Two things an operator reaches for in an incident: the log, and the switch that stops a database. The first lived in a file on another machine; the second was a delete. This release puts both in the monitoring catalogue.


The log
- In memory, as tables The last 5,000 lines and, apart, the last 1,000 warnings and errors; a groups table by level, logger and message pattern with digits folded; a loggers table with line counts.
- Levels changed live An UPDATE on a logger's level changes it in the running JVM until restart; null inherits; an unknown word is refused.
- Fed by the configurator The root and every standard logger copy lines into the buffer, and a property leaves it out.
Lifecycle
- Start, stop, restart Actions on a database and a server, gated by state, served by one action service, so SQL, JMX and buttons share one implementation, one set of preconditions and one audit trail. A refused write says which state the resource is in.
- Only what is admitted A row lists the actions it admits right now, and a button is enabled when its verb is listed. A closed database is forgotten so the next request builds it anew; before, it was unusable until the JVM restarted.
- Environments by criticality Production, configuration, QA, test, demo, development and unknown, each in a colour legible under white text, carried by servers and inherited by databases.
Statement times now read as durations, from milliseconds to hours, because a fixed unit read badly at both ends.