Purpose
This guide explains how an administrator can monitor:
- the users currently configured in Giotto
- the clients currently configured in Giotto
- the active sessions in the platform
- the access activity over time
- the details of individual access events
By the end of this guide, you will know where to look in Keycloak and VictoriaLogs to understand who is using the platform and what they are accessing.
Overview
In Giotto, there are two important identity types to keep in mind:
- a user is usually a person accessing the platform
- a client is usually an application, such as a Python app, connecting programmatically through OAuth2
Both are managed through Keycloak, while detailed access activity can be monitored through VictoriaLogs.
A practical monitoring workflow is:
- inspect users and clients in Keycloak
- inspect the currently active sessions in Keycloak
- inspect access history and request activity in VictoriaLogs
- open individual events in VictoriaLogs to see detailed request information
Before you begin
Make sure you have:
- administrator access to Keycloak
- access to the Logs section in Giotto
- permission to inspect the
giottorealm
Step 1 — Open Keycloak and go to the giotto realm
Start by opening the Keycloak admin interface and logging in as an administrator.
Then:
- move to the
giottorealm
This is the realm where the platform users and clients are managed.
Step 2 — Inspect users and clients
Inside the giotto realm, inspect both:
- the Users section
- the Clients section
These two views tell you who and what is configured to access the platform.
How to interpret them
Users
A user usually represents a person.
This is the identity type used when a human logs into the platform through the UI or other human-facing flows.
Clients
A client usually represents an application.
For example, a Python application using the Giotto Python client is represented in Keycloak as a client. That application authenticates through OAuth2 and then uses its client credentials to connect to the platform.
So, in practical terms:
- a person is usually a user
- a programmatic application is usually a client
Step 3 — Check the currently active sessions
Still inside Keycloak, you can inspect the currently active sessions.
This allows you to see which users or clients are actively connected or have active authentication sessions.
Why this matters
The active sessions view is useful when you want to answer questions such as:
- who is currently logged in
- which sessions are still active
- whether a given user or application has a live session right now
This is the best place to inspect current session state.
Step 4 — Monitor access over time in the Logs section
If you want to inspect access activity over time rather than only current sessions, go to the Logs section in Giotto.
This opens VictoriaLogs.
From there, you can query logs by:
- user email
- last name
- other identifying information available in the logs
You can also adjust the time interval to focus on the period you want to inspect.
Example monitoring approach
A common workflow is:
- identify the user or client you want to inspect
- search by email or name in VictoriaLogs
- narrow the time range
- inspect the returned events
This is the best way to understand access behavior over time.
Step 5 — Open an event to inspect request details
In VictoriaLogs, once you find a relevant event, click on it to open the full event details.
There, you can inspect more detailed information about the request, such as:
- which resource was being accessed
- what kind of request was made
- when it happened
- which user or client generated it
Why this matters
This is the key step when you want to move from “who accessed the platform” to “what exactly did they try to access”.
It is useful for:
- auditing
- troubleshooting
- understanding usage patterns
- verifying whether access rules are being applied as expected
Typical monitoring scenarios
Check which users exist in the platform
Go to Keycloak → giotto realm → Users.
Check which applications can connect programmatically
Go to Keycloak → giotto realm → Clients.
Check who is active right now
Use the active sessions view in Keycloak.
Check who accessed something yesterday or last week
Use VictoriaLogs and set the appropriate time range.
Check which resource a user or client tried to access
Open the specific log event in VictoriaLogs and inspect its details.
Key distinction: current state vs historical access
A useful way to think about the tools is:
- Keycloak shows the identity configuration and current session state
- VictoriaLogs shows the historical access activity
So:
- if you want to know who exists and who is currently active, start in Keycloak
- if you want to know what happened over time, start in VictoriaLogs
Best practices
Check both users and clients
Do not focus only on human accounts. Programmatic applications may also be actively accessing the platform.
Use time filters in VictoriaLogs
Historical logs are much easier to inspect when the time range is narrowed.
Search by stable identifiers
Email is usually a good search key for users. Client names or other known identifiers may help for application access.
Open individual events for real context
The event list is useful, but the expanded event view is what gives the most actionable detail.
Troubleshooting tips
I cannot find the user in logs
Make sure:
- you are using the correct email or identifier
- the time range is wide enough
- the access event actually happened in the selected interval
I see the user in Keycloak but not in active sessions
That usually means the user exists but is not currently logged in.
I see a client in Keycloak but cannot tell what it accessed
Go to VictoriaLogs and search for activity related to that client over the relevant time window.
The logs are too noisy
Filter more narrowly by:
- last name
- time interval
- other known event attributes
Summary
To monitor users, clients, and access activity in Giotto:
- use Keycloak in the
giottorealm to inspect Users and Clients - use Keycloak to inspect active sessions
- use VictoriaLogs to inspect access activity over time
- open individual events in VictoriaLogs to inspect request details and accessed resources
This gives administrators both:
- a live identity/session view
- a historical access/audit view
Comments
0 comments
Article is closed for comments.