ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

The server log as a table with live levels, and start, stop, restart as actions

The node keeps its last 5,000 log lines and 1,000 warnings and errors in memory as queryable tables, and a logger's level changes with an UPDATE. Databases and servers start, stop and restart through one action service.

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 Server log page: tiles for errors and warnings in the last hour, lines per minute, top logger and error patterns, and the list of error and warning lines with logger, thread and message.
The last thousand warnings and errors, as a table.
The Log levels page: one row per logger with its effective level, errors, warnings and lines since start.
Loggers with their live levels. An UPDATE on a row changes one.

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.