Repository navigation
v2.17.0
Structured audit events
Every audited action is now one event with its own fields, so you can filter on what was done instead of parsing the message:
mustafa: deployment.list success boh-cy/* on Zenia-NonProd
mustafa: deployment.restart success boh-cy/boh on Zenia-NonProd
event.action : "deployment.restart" and event.outcome : "failure"
openconsole.verb : "exec" and openconsole.cluster : "Zenia-NonProd"
openconsole.replicas_to >= 10
Audit events
actionis<resource type>.<verb>(deployment.list,deployment.restart,pod.exec,secret.reveal,user.login,permission.create). The result is a separateoutcome(success/denied/failed/rate_limited/locked) with areason(forbidden,conflict,k8s_forbidden,bad_password, …).- Details are typed fields instead of a
(k=v)suffix on the resource name:restarted_at,replicas_from/replicas_to,exit_code/bytes_in/bytes_out/duration_ms,key(never the value),dry_run/yaml_from/yaml_to,login_method,grant,changed,error, … - Every event records who and from where: source IP, user agent, account source (
local/ldap/azure), request id. - The cluster is the one the action targeted: empty for sign-ins, users, groups, roles, settings and sessions (it used to be the admin's selected cluster); a permission grant records the grant's cluster; plus
cluster_id. - Reads refused for lack of permission are audited as
denied. Lists the UI fetches on its own (the dashboard's 10-second refresh, the namespace list behind the command palette and the role editor) are not audited. - One stdout line per action. The extra
deployment.action,workload.action,secret.action,yaml.apply,recording.action,pod.exec.start/end,*.logs.start,user.password_reset,user.auto_provisionlines and thelevel=errorlines repeating a failed action are gone.level=erroris left for faults in OpenConsole itself.
ECS
event.actionwithout the outcome,event.outcome,event.typefrom the verb,event.category,event.reason;openconsole.verb,openconsole.outcome,openconsole.auth_source,openconsole.cluster_idand the details asopenconsole.<key>.
Admin → Audit Logs
- Outcome badge, Verb / Resource type / Cluster filters, expandable details per row; the CSV export has a column per field.
deploy/elk
- Mappings for every detail with its type (dates, longs, booleans), and
event.reason. - The pipeline gives 2.16 audit lines the 2.17 shape, so one query finds old and new events.
- Verified on Elasticsearch 8.15.3 and 9.1.0.
Upgrade notes
- Audit rows already in the database are converted on the first start (action, verb, outcome, singular resource type). Their resource names keep the old
(k=v)suffix until retention removes them. - Re-run
deploy/elk/install.sh. The new mapping applies from the next rollover (POST logs-openconsole.audit-default/_rolloverto apply it now). - Breaking for Kibana: saved searches, visualizations and alerts on
event.action : *.success/*.denied/login.*must move toevent.action+event.outcome.?action=deployment.restart.successstill works in the audit API.
See Audit events in the README.