How do I use the operations journal?

Requires Pro

Quick answer

The journal lives in the Operations area, on the Journal tab, and documents system and job events. Use “Add Journal entry” to record an occurrence: Source, Level, Event and, optionally, a Message. Typically, automated processes (cron, system) write here — but you can also create entries manually.

Prerequisites

Operations is part of the Operations module and is available from the Pro tier. Without this license, the server returns 403.

Open Operations → Journal. Choose Operations in the left-hand navigation, then the Journal tab. The table shows the events with Source, Level and Event.

Screenshot pending betrieb-journal-01 Operations area with the Journal tab active and a list of events

The 'Journal' tab in the Operations area.
Create an entry. Click “Add Journal entry” and fill in the dialog:
- Source (required) — origin, e.g. cron, system, backup.
- Level (required) — Information, Warning or Error.
- Event (required) — a short identifier, e.g. backup.completed.
- Message (optional) — free-text details.
Screenshot pending betrieb-journal-02 'Add Journal entry' dialog with Source, Level, Event and Message

A journal entry: source, level, event and an optional message.
Save. The entry appears in the journal list immediately.

The journal is a POST to /api/v1/journal (scope write). source and event are required; level defaults to info.

curl -X POST https://demo.notory.io/api/v1/journal \
  -H "Authorization: Bearer inv_dein_token" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "cron",
    "level": "info",
    "event": "backup.completed",
    "message": "Nächtliche Sicherung erfolgreich (128 Assets)"
  }'

{
  "id": "e1a2…",
  "tenant_id": "3d9b0c12-…",
  "source": "cron",
  "level": "info",
  "event": "backup.completed",
  "message": "Nächtliche Sicherung erfolgreich (128 Assets)",
  "created_at": "2026-07-08T02:00:04Z",
  "updated_at": "2026-07-08T02:00:04Z"
}

List entries with GET /api/v1/journal (newest first).

Possible errors: 401 (token missing/invalid), 403 (the Operations module is not in your tier or no write access), 422 (validation).

What happens behind the scenes?

Tenant-bound: Every entry belongs to your current tenant and is invisible to others.
Retention: Under Administration → Configuration → Journal retention (days), administrators define after how many days journal entries are automatically deleted (0 = keep forever).
Journal ≠ audit log: The journal can be freely populated (system/job events). The audit log, by contrast, automatically logs every write action a user performs and cannot be written to manually.
No automatic delivery: A journal entry does not trigger an e-mail. For delivery to recipients, use Notifications.