Wiki source code of DDAudit – Rapports d’état du serveur
Last modified by jhurst on 2024/04/02 14:25
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
1.1 | 1 | This document describes the DDAudit reports available in server status page. |
2 | |||
3 | {{ddtoc/}} | ||
4 | |||
5 | = DDAudit Security = | ||
6 | |||
7 | == Security Audit Events List (30 days) == | ||
8 | |||
9 | __Columns description__ | ||
10 | |||
11 | **Event Date**: Date and time of the event in MM/DD/YYYY HH:mm:ss (en). | ||
12 | |||
13 | **Event Id**: Global counter to identify the event. | ||
14 | |||
15 | **Event Name**: Type of the event. Possible types are: | ||
16 | |||
17 | * **Login**: Connection of a user in DigDash Enterprise. | ||
18 | * **AccountCreation**: Creation of a user (target) by an administrator. | ||
19 | * **AccountRemoval**: Removal of a user (target) by an administrator. | ||
20 | * **AccountUpdate**: Update of a user (target) by an administrator. | ||
21 | * **PasswordChange**: Modification of the password of a user (target), done by himself (must change password or forgot password workflows), or by an administrator. | ||
22 | * **PasswordReset**: Request for a password reset code of a user (target) (forgot password workflow). | ||
23 | * **ACLChange**: Add or removal of an ACL (Access Control List) to/from a user (target), or to/from an ACL Group, by an administrator. DigDash ACL are internal authorizations for DigDash Enterprise. Example: Admin > Access Server Settings, Scheduler > Schedule refresh (Please refer to DigDash configuration documentation). | ||
24 | * **ACLGroupChange**: Add or removal of an ACL Group (Access Control List Group) to/from a user (target) by an administrator. | ||
25 | * **HackAttempt**: Hack attempt. Examples: Cross Site Request Forgery, Code injections... (see advanced configuration guide for different types of hacks). | ||
26 | |||
27 | **User**: Name of the user __who did__ the corresponding action. | ||
28 | |||
29 | **Target User**: Name of the user who is the target for the action. | ||
30 | |||
31 | **IsAdmin**: A boolean that flags if the target user is an administrator (true) or not (false). | ||
32 | |||
33 | **Client Type**: The DigDash module used to do the action (see last chapter) | ||
34 | |||
35 | **Status**: The action was successful applied (SUCCESS) or failed (FAILED) | ||
36 | |||
37 | **Error**: In case the action has failed, this column is the error code. Please refer to Error Codes documentation in DigDash documentation folder. | ||
38 | |||
39 | **Details**: Depending on the event, this columns contains additional details. Non-exhaustive list of possible details per event name: | ||
40 | |||
41 | * **Login**: The error message corresponding to the error code | ||
42 | * **AccountCreation**: Details about the added LDAP attributes to create the user. Example: displayName,userPassword,uid,description,objectclass,sn,cn | ||
43 | Or the error message returned by LDAP | ||
44 | * **AccountRemoval**: The error message returned by LDAP | ||
45 | * **AccountUpdate**: Details about added, modified(U) or removed LDAP attributes. In the case of the description attribute it also contains the updated description field. Example: (U)userPassword (~*~*~*~**),(U)description (mustChangePassword=no) | ||
46 | Or the error message returned by LDAP | ||
47 | * **PasswordChange**: The error returned by LDAP | ||
48 | * **PasswordReset**: The email address of the recipient for the reset code, or an error message | ||
49 | * **ACLChange**: Details about the added or removed ACL or modified(U) ACL Group. Example: ACL:EditDataSourceForGroup | ||
50 | * **ACLGroupChange**: Details about the added or removed ACL groups. | ||
51 | |||
52 | = DDAudit SESSIONS = | ||
53 | |||
54 | == Session List (30 days) == | ||
55 | |||
56 | __Columns description__ | ||
57 | |||
58 | **User**: User login name | ||
59 | |||
60 | **Client Type**: The DigDash module used to do the action (see last chapter) | ||
61 | |||
62 | **User Agent Name**: User Agent String sent by the user’s browser (Chrome, Firefox…). Internal client (Scheduler, FilesGC, adminConsole) do not send a User agent name | ||
63 | |||
64 | **User Agent Name**: Browser version | ||
65 | |||
66 | **User Agent OS**: Name of the operating system of the user’s computer | ||
67 | |||
68 | **Start Time**: Date and time of the start of the session in MM/DD/YYYY HH:mm:ss (en) | ||
69 | |||
70 | **Status**: Current status of the session | ||
71 | |||
72 | * **ACTIVE**: currently active session | ||
73 | * **CLOSED**: closed (logout or timeout) | ||
74 | * **NOT ACTIVE**: opened but never closed. Typically the server has been stopped in the meanwhile | ||
75 | * **FAILED**: failed to log in | ||
76 | |||
77 | **Error**: In case the action has failed, this column is the error code. Please refer to Error Codes documentation in DigDash documentation folder. | ||
78 | |||
79 | **Duration**: Duration in seconds of the session since its start (ACTIVE or CLOSED status) | ||
80 | |||
81 | = DDAudit Flows = | ||
82 | |||
83 | There are two reports for the flows: | ||
84 | |||
85 | * The flow refresh history concerns the refresh of flows (scheduler and manual refreshes) | ||
86 | * The flow usage history concerns viewing of the flow content | ||
87 | |||
88 | == Flows Refresh List (30 days) == | ||
89 | |||
90 | __Columns description__ | ||
91 | |||
92 | **Flow Name**: Name of the flow | ||
93 | |||
94 | **Role Id**: Identifier of the flow’s role | ||
95 | |||
96 | **Synchronization Date**: Date and time of the refresh in MM/DD/YYYY HH:mm:ss (en) | ||
97 | |||
98 | **Device**: Device for which the refresh has been done | ||
99 | |||
100 | **User**: User for whom this refresh has been done (by himself or by the scheduler) | ||
101 | |||
102 | **Client Type**: The DigDash module used to do the action (see last chapter) | ||
103 | |||
104 | **Event**: Name of the event used to refresh the flowThe DigDash module used to do the action (see last chapter) | ||
105 | |||
106 | **Status**: Status of the refresh (OK or ERROR) | ||
107 | |||
108 | **Error**: In case the action has failed, this column is the error code. Please refer to Error Codes documentation in DigDash documentation folder. | ||
109 | |||
110 | == Flows Usage List (30 days) == | ||
111 | |||
112 | __Columns description__ | ||
113 | |||
114 | **Event Id**: Global counter to identify the event | ||
115 | |||
116 | **Flow Name**: Name of the flow | ||
117 | |||
118 | **Role Id**: Identifier of the flow’s role | ||
119 | |||
120 | **User**: User login name | ||
121 | |||
122 | **View Date**: Date of the visualization in MM/DD/YYYY HH:mm:ss (en) | ||
123 | |||
124 | **Client Type**: The DigDash module used to do the action (see last chapter) | ||
125 | |||
126 | **Status**: Status of the view (OK or ERROR) | ||
127 | |||
128 | **Error**: In case the action has failed, this column is the error code. Please refer to Error Codes documentation in DigDash documentation folder. | ||
129 | |||
130 | = DDAudit CUBES = | ||
131 | |||
132 | There are two reports for the cubes: | ||
133 | |||
134 | * The cube refresh history concerns the refresh of cubes (scheduler and manual refreshes) | ||
135 | * The cube usage history concerns viewing of the cube content (from a flow) | ||
136 | |||
137 | == Cubes Refresh List (30 days) : Last 30 days of cubes refresh history(monthly) == | ||
138 | |||
139 | __Columns description__ | ||
140 | |||
141 | **Data Model**: Name of the cube’s data model | ||
142 | |||
143 | **Role Id**: Identifier of the flow’s role | ||
144 | |||
145 | **User**: User login name | ||
146 | |||
147 | **Cube Date**: Date of the refresh in MM/DD/YYYY HH:mm:ss (en) | ||
148 | |||
149 | **Status**: Status of the refresh (OK, ERROR or UNKNOWN). UNKNOW status means that DDAudit has no information about the refresh of cube, but it exists on the server’s hard drive. | ||
150 | |||
151 | **Error**: In case the action has failed, this column is the error code. Please refer to Error Codes documentation in DigDash documentation folder | ||
152 | |||
153 | **Refresh Time**: Duration of the refresh operation in milliseconds | ||
154 | |||
155 | **Cube File Size**: Size of the cube’s files on the hard drive | ||
156 | |||
157 | **Cube Rows Count**: Number data rows in the cube | ||
158 | |||
159 | **Nb Parts**: Number of part files for the cube. Each part is roughly 100MB (compressed) | ||
160 | |||
161 | == DDAudit Cubes Usage List (30 days) == | ||
162 | |||
163 | //* Expand is the name we give to the extraction and aggregation of data from a cube based on a selection (filters, drill, view..)// | ||
164 | |||
165 | __Columns description__ | ||
166 | |||
167 | **Event Id**: Global counter to identify the event | ||
168 | |||
169 | **Data Model**: Name of the cube’s data model | ||
170 | |||
171 | **User**: User login name | ||
172 | |||
173 | **Expand Date**: Date of the usage of the cube in MM/DD/YYYY HH:mm:ss (en) | ||
174 | |||
175 | **Expand Type**: Type of usage: | ||
176 | |||
177 | * **dumpJSON**: A flow visualization, filter, drill… | ||
178 | * **dumpStruct**: Extraction of cube metadata for data model editing (members, hierarchies...) | ||
179 | * **dumpExcel**: Excel export (with style) | ||
180 | * **excelExport**: Excel export (without style) | ||
181 | * **csvExport**: CSV Export | ||
182 | * **checkDeviceCondition**: Condition solving for flow publishing | ||
183 | |||
184 | **Status**: Status of the expand (OK or ERROR) | ||
185 | |||
186 | **Cache**: Expand result cube was retrieved from Result cube cache (TRUE/FALSE) | ||
187 | |||
188 | **Error**: In case the action has failed, this column is the error code. Please refer to Error Codes documentation in DigDash documentation folder | ||
189 | |||
190 | **Cube Rows Count**: Number data rows in the cube | ||
191 | |||
192 | **Result Rows Count**: Number of data rows in the result cube | ||
193 | |||
194 | **Expand Time**: Duration of the expand operation in milliseconds | ||
195 | |||
196 | = DDAudit System = | ||
197 | |||
198 | == Memory Usage (24 hours) == | ||
199 | |||
200 | This line chart shows the evolution of memory usage in the last 24 hours. | ||
201 | |||
202 | == CPU Usage (24 hours) == | ||
203 | |||
204 | This line charts shows the usage of CPU in the last 24 hours. The dark blue line is the usage of CPU by DigDash Enterprise server components only. The light blue line is the usage of CPU by the whole system, including DigDash Enterprise server components. | ||
205 | |||
206 | == Storage Usage (24 hours) == | ||
207 | |||
208 | This line shows the relative cumulative amount of data written to the disk (line goes up) or deleted from the disk (line goes down, negative value is possible) in the last 24 hours. The reference (zero) is read at the start of the server. | ||
209 | |||
210 | Note: Other processes on the computer may affect this chart, as they write or delete files on the disk. | ||
211 | |||
212 | = VOCABULARY = | ||
213 | |||
214 | **Client Type**: The DigDash module used to do the action: | ||
215 | |||
216 | * **<empty>**: Settings pages | ||
217 | * **AdminConsole**: DigDash enterprise Studio (java client) | ||
218 | * **Scheduler**: Background scheduler which refreshes flows based on schedules or events | ||
219 | * **Dashboard**: Dashboard application (web-based) | ||
220 | * **FilesGC**: DigDash Enterprise maintenance service |