GLog — using the Board (web UI)
The Board is GLog’s web app for humans: operators, auditors and security teams read and
investigate the audit trail visually — no code. It’s a read client over the same API described
in integration-methods.md (Method B).
- Live: https://glog.gstack.esempla.systems
- Auth: JWT — either Keycloak login (realm
interdictii, clientglog-web, PKCE) or GLog’s own username/password. What you can see/do depends on your scopes (audit:read/:write/:admin) and yourtenant. Seeauth-and-integrations.md.
1. Signing in
Section titled “1. Signing in”Open the URL → the login screen offers, depending on how the backend is deployed:
- Keycloak — one click, redirects to the
interdictiirealm; your realm roles map to GLog scopes. - Username / password — GLog’s own accounts (HS512 token stored in the browser).
- Demo — auth bypassed (dev only).
Your tenant is shown in the left rail under your name. Every screen is tenant-scoped — you only ever see your tenant’s events.
2. The screens
Section titled “2. The screens”The left rail groups the screens:
Monitorizare
Section titled “Monitorizare”- Tablou de bord — KPIs (events, error rate, active services), volume over time, latest events.
- Căutare jurnale — the workhorse log search (details in §3).
- Căutare corelată — paste a
correlation-id(or click one in the search table) to reconstruct the cross-service flow of a single request: a timeline + the ordered events. Answers “why didn’t X happen?”. Filters here are collapsible too.
Analiză
Section titled “Analiză”- Servicii — every system emitting logs: volume, error rate, last activity, health.
- Transparență — public-interest / transparency view over the trail.
Conformitate
Section titled “Conformitate”- Integritate — verifies the hash chain (
hash/prevHash) per(tenant, service)and flags any break — the tamper-evidence check. - Arhivă — long-term/segmented archive access.
Sistem
Section titled “Sistem”- Administrare — admin-only (
audit:admin): replay/forward, integrity runs, operational bits.
Note: there used to be a separate Securitate screen; it duplicated Căutare jurnale, so it was removed. Filter Căutare jurnale by the relevant operations (e.g.
LOGIN,ACCESS_DENIED) and status instead.
3. Căutare jurnale — filters
Section titled “3. Căutare jurnale — filters”The filter bar sits under the title and can be collapsed/expanded with the ▸ Filtre / ▾ Ascunde filtrele button (top-right of every filtered page).
- Perioadă — a single control. Click it for quick presets Ultimele 24 ore / 7 zile / 30 zile or a custom De la / Până la range, then Aplică. Default = last 24 hours.
- Serviciu — pick one service (options come from the loaded events).
- Operație — a searchable, multi-select dropdown. Type to filter, tick several operations; selected ones show as removable chips. Operations are derived from the event stream (the same source as Servicii). Leave empty for all.
- Tip obiect — server-side object-type filter (e.g.
PAYMENT). - Pe pagină — page size (20 / 50 / 100).
- ⌕ Caută — run the query; pager below the table walks pages.
The results table has its own free-text search box and expandable rows (full event detail, actor/IP, correlation-id link → Căutare corelată).
4. Board vs headless
Section titled “4. Board vs headless”The Board never does anything the API can’t — it’s Method B in
integration-methods.md. For automation, dashboards in your own
tools, or bulk export, use Method A (the API / SDKs) with a service
token.