You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: identity-and-access-management/audit-trail/concepts.mdx
+17-5Lines changed: 17 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,10 +10,6 @@ dates:
10
10
validation: 2024-11-26
11
11
---
12
12
13
-
## Action
14
-
15
-
An action in the context of Audit Trail is the method performed on any of your Scaleway resources throught the API.
16
-
17
13
## Audit Trail
18
14
19
15
Audit Trail is a tool that holds a record of events and changes performed within a Scaleway Organization. Audit Trail allows you to keep track of all actions, whether successful, attempted, or failed, perfomed on your Scaleway resources.
@@ -26,8 +22,24 @@ Audit Trail allows you to view the metadata of the API method used, allowing you
26
22
27
23
An event is a log of user activity on your Scaleway resources.
28
24
25
+
## Locality
26
+
27
+
In the context of Audit Trail, locality refers to the place where the Scaleway resources being monitored are located. They can be located in different Scaleway Projects, or Organizations.
28
+
29
+
## Method
30
+
31
+
A method in the context of Audit Trail is the API call sent to the Audit Trail API whenever a principal takes an action (whether successful, attempted, or failed) on any Scaleway resource.
32
+
29
33
## Region
30
34
31
35
A region is the geographical area in which your resources are located. They are duplicated on all [Availability Zones](/compute/instances/concepts/#availability-zone) of the selected region (Paris, Amsterdam, or Warsaw).
32
36
33
-
Audit Trail allows you to select your resources by region. This allows you to better sort through your resources.àction`
37
+
Audit Trail allows you to select your resources by region. This allows you to better sort through your resources.
38
+
39
+
## Status
40
+
41
+
A status is the API response returned whenever an action was taken on a resource by a principal. There are two statuses:
42
+
43
+
- Successful: this means that the API request was executed.
44
+
45
+
- Failed: this means that the API request has failed.
0 commit comments