Skip to content

Commit 0615a55

Browse files
committed
Migrate Audit Logging from V1 to V2 docs
1 parent bd5ed98 commit 0615a55

File tree

2 files changed

+31
-0
lines changed

2 files changed

+31
-0
lines changed
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
id: migrate-audit-logging
3+
title: Migrate Audit Logging
4+
description: Learn to migrate from V1 to V2 audit logging by changing the search queries.
5+
---
6+
7+
<p><a href="/docs/beta"><span className="beta">Beta</span></a></p>
8+
9+
import useBaseUrl from '@docusaurus/useBaseUrl';
10+
11+
This document outlines the migration process from V1 to V2 audit logging by modifying the search queries. The `filterPredicate` field in V1 audit logging is replaced with `logAlayticsFilter`, `auditDataFilter`, and `securityDataFilter` fields in V2. In addition, we have also added `selectionType` and `selectedViews` fields (what benefit with this?)
12+
13+
Currently, both the log lines of V1 and V2 will be accessible for RBAC indexes query.
14+
15+
:::note
16+
V2 changes are only applicable for `RoleUpdate` and `RoleCreated` events.
17+
:::
18+
19+
<br/><img src={useBaseUrl('img/users-roles/JSON-diff-V1-V2.png')} alt="JSON-diff-V1-V2" style={{border: '1px solid gray'}} width="800"/>
20+
21+
For example, consider you are interested in searching a customer-specific query with a change in `roleupdated` or `rolecreated` events. Now, if you perform this search you will initially see the V1 type of event in the search results. However, to view the results with the V2 event type, you are required to adjust the parameters in the query.
22+
23+
```sql title="V1 Audit Logging"
24+
25+
26+
```
27+
28+
```sql title="V2 Audit Logging"
29+
30+
31+
```
1.07 MB
Loading

0 commit comments

Comments
 (0)