| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Introduction
The tags beginning with auth.keycloak identify events generated by Keycloak.
Tag structure
The full tag must have 4 levels. The first two are fixed as auth.keycloak. The third level identifies the type of event sent and the fourth level identifies the subtype.
...
Technology
...
Brand
...
Type
...
Subtype
...
auth
...
Keycloak
...
user
...
event
There are the valid tags and corresponding data tables that will receive the parser’s data:
Product / Service |
|---|
Tag
Data table
...
Tags | Data tables | |
|---|---|---|
Keycloak |
|
|
For more information, read more About Devo tags.
Table structure
These are the fields displayed in this table:
auth.keycloak.user.event
Field | Type | Extra fields |
|---|---|---|
auth_method |
| |
auth_session_parent_id |
| |
auth_session_tab_id |
| |
auth_type |
| |
client_id |
| |
code_id |
| |
error |
| |
event_time |
| |
eventdate |
| |
executor_thread |
| |
hostchain |
| ✓ |
hostname |
| |
ip |
| |
log_level |
| |
rawMessage |
| ✓ |
realm_id |
| |
redirect_uri |
| |
tag |
| ✓ |
user_id |
| |
username |
|