Audit and Logging

In SPG99, it is useful to distinguish between several layers of observability and audit.

1. Activity in Console

Activity shows actions initiated through the user interface:

• tenant creation;
• database creation or deletion;
• UI operation errors;
• task completion status.

This is a practical user-facing log that is convenient for everyday work.

2. Control Plane events and API operations

At the Control Plane level, the following matter:

• the lifecycle of API keys;
• creation and deletion of tenants and databases;
• changes of resource states;
• the /v2/events stream, which lets Console update the catalog quickly.

3. Database logs

These are the actual PostgreSQL / compute logs:

• SQL errors;
• startup failures;
• bootstrap problems;
• application-level messages inside the database.

Why this separation matters

• Activity answers the question “who clicked what in the UI”;
• the Control Plane answers the question “how did the resource state change”;
• database logs answer the question “what actually happened inside PostgreSQL.”

In a good diagnostic workflow, these three layers complement each other.