Wiki source code of État du serveur

Last modified by Aurelie Bertrand on 2025/02/07 10:18
Show last authors
1 {{ddtoc/}}
2
3 ----
4
5 This page is used to monitor the status of the server and activate a set of services.
6
7 [[image:Server_status_page_FR.png]]
8
9 = General status =
10
11 This section is mainly used to view system information (versions installed, memory, etc) and download server logs.
12
13 |=(% scope="row" style="width: 370px;" %)Memory (occupied/max)|(% style="width:795px" %)(((
14 Displays occupied and available memory.
15 Click on the [[image:1710249675342-408.png]] button reclaims memory space using the garbage collector. This allows you to manage memory, in particular by freeing memory for objects that are no longer in use.
16 )))
17 |=(% style="width: 370px;" %)(((
18 Memory overview
19
20 [[image:1710250381866-493.png]]
21 )))|(% style="width:795px" %)(((
22 Gives an overview of memory usage in the form of a progress bar:
23
24 * In light blue: the actual amount of memory used
25 * In blue: the amount of memory reserved
26 * In white: the maximum amount that the application will be able to use
27
28 Clicking on the preview bar displays a window listing the quotas defined. See the paragraph [[Quota management>>doc:Digdash.deployment.configuration.configuration_guide.Cluster_parameters.WebHome||anchor="quota"]] for more details.
29 )))
30 |=(% style="width: 370px;" %)Working directory (AppData)|(% style="width:795px" %)(((
31 Path to the working directory.
32 Click on the icon [[image:1710250771783-246.png]] icon will take you to the configuration details in the digdash.properties file.
33 A link will take you to the [[documentation>>doc:Digdash.deployment.configuration.advanced_system_guide.other_advanced_parameters.WebHome]] for more information.
34
35 [[image:Configuration_details_window_FR.png||alt="Détails configuration"]]
36 )))
37
38 == Download server logs ==
39
40 To retrieve the server logs, click on **Log level 'debug' | Current log level 'info' then __Download the log file.__**
41
42 The logs are particularly useful in the event of an error in your support request.
43
44 = Scheduler =
45
46 This section** allows you to **start/stop the scheduler and view its information.
47
48 The scheduler must be started for refresh programming to work. If it is stopped, click on [[image:https://doc.digdash.com/xwiki/wiki/dev/download/Digdash/user_guide/studio/Schedule_refresh/WebHome/1706526467080-910.png?width=16&height=18&rev=1.1||alt="1706526467080-910.png" height="18" width="16"]].
49 The scheduler user must also be entered.
50 See the page [[Schedule refreshes>>doc:Digdash.user_guide.studio.Schedule_refresh.WebHome]] page for more details.
51
52 You can check if there are any scheduled tasks to run by clicking on the [[image:1710254700486-368.png]] icon at the end of the **Last check date** line.
53
54 = Maintenance service =
55
56 This section** allows you to **start/stop the maintenance service and view information about the operations performed.
57
58 The maintenance service consists of :
59
60 * A file cleaner (also known as Files GC) which cleans up all unused files: old history files, cubes and other {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}}-dependent files.
61 * An automatic configuration backup
62
63 See the [[Automatic Maintenance Service>>doc:Digdash.deployment.configuration.advanced_system_guide.Automatic_maintenance.WebHome]] page for a detailed description.
64
65 To start this service, (% id="cke_bm_2197S" style="display:none" %)click (%%)on [[image:https://doc.digdash.com/xwiki/wiki/dev/download/Digdash/user_guide/studio/Schedule_refresh/WebHome/1706526467080-910.png?width=16&height=18&rev=1.1||alt="1706526467080-910.png" height="18" width="16"]] at the end of the **Maintenance service started** line.
66
67 By default, maintenance takes place at midnight. You can start the file cleaner immediately by clicking on the icon [[image:1710254700486-368.png]] icon at the end of the **Next maintenance date** line.
68
69 = Audit services =
70
71 This section** allows you to **start the DigDash data audit services you wish to use (session audit service, cubes, flows, etc).
72
73 Click on the [[image:https://doc.digdash.com/xwiki/wiki/dev/download/Digdash/user_guide/studio/Schedule_refresh/WebHome/1706526467080-910.png?width=16&height=18&rev=1.1||alt="1706526467080-910.png" height="18" width="16"]] icon to activate the desired audit services.
74 Pre-defined reports can be accessed directly from the **Choose an audit report **drop-down list **... **See the page [[DDAudit - Server status reports>>doc:.ddaudit_notice.WebHome]] for details of the reports.
75
76 See the [[Deployment of the audit module>>doc:Digdash.deployment.configuration.ddaudit_module_install.WebHome]] page for details of the audit module.
77
78 = Sessions =
79
80 This section allows you to view general session information.
81
82 You can click on the** List **link next to **Number of Sessions (Total / Scheduler) **to view details of active sessions.
83
84 You can disable authentication for all users by clicking on the [[image:1710259471051-331.png]] icon on the **Activate authentication** line. This disables the server and prevents all users from connecting.
85 ❗Only(% style="color:#c0392b" %)**the super-user can connect to a disabled server.❗**
86
87 = Refresh engine =
88
89 This section allows you to view in-memory cube information and synchronisation tasks.
90
91 == Cubes in memory ==
92
93 You can click **List** to the right of **Number of cubes and Shares of cubes in memory **to view details of cubes in memory.
94 [[image:Cubes_in_memory_window_FR.png||alt="Cubes en mémoire"]]
95
96 (% class="wikigeneratedid" id="H" %)
97 The **Attributes** column gives the following information about the cubes:
98
99 * **I**: Interactive use (used by flows and dashboards)
100 * **M**: In memory only
101 * **N**: Unmanaged (temporary, deleted, in generation, etc.)
102 * **B**: Cube in generation. Cube generation can be stopped by clicking on the [[image:1710249675342-408.png]] button in front of the cube name (or by ticking the box and then **Deleting**).
103 * **L**: Live data cube
104
105 You can delete cubes in memory by checking the corresponding box and then clicking on the **Delete **button or(% id="cke_bm_3342S" style="display:none" %) by (%%)clicking on the [[image:1710249675342-408.png]](% id="cke_bm_3342E" style="display:none" %) button for (%%)each one.
106
107 == Synchronisers ==
108
109 Synchronisers are in charge of cube synchronisation tasks:
110
111 * **"PlayTP" **: interactive tasks (launched by the user). For example, the user synchronises a {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} in the Studio or refreshes it from the dashboard.
112 * "**SyncTP": **scheduled tasks. These are mainly tasks relating to the scheduling of refreshes. They also include {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} synchronisation tasks for users other than the logged-in user.
113 * "**CopyTP": **tasks for sending exports to their destination (devices: file server, email, SMS, etc).
114 * "**ExportTP": **conversion tasks into the format requested for the export. For example, when a user exports a graphic as a PDF.