Differences

This shows you the differences between two versions of the page.

--- admin:the_log [2018/10/03 01:44] – [Custom query] mark
+++ admin:the_log [2023/01/24 09:53] (current) – Gary Willetts
@@ Line 1: / Line 1: @@
-{{indexmenu_n>140}}
+{{indexmenu_n>196}}
-=====The log =====
+====== 25.19. The system log ======
 The log contains records of who did what and when in the system. It's a useful place to look to find out what happened to certain records and when certain things were done. Some events (lots!) are always logged by mSupply but some are optional and are chosen in the //Log// tab of the [[preferences:general#log|General preferences]] page.
@@ Line 6: / Line 6: @@
 {{ :admin:view_log.png?700 |}}
+The columns contain this information:
+  * **Date:** the date when the log entry was made.
+  * **Time:** the time the log entry was made.
+  * **User:** the name of the user who did the operation giving rise to the log entry.
+  * **Type:** the type of log entry. Can be used for filtering or just telling you which part of the system generated the log entry.
+  * **Event:** a description of the event that occurred.
+  * **Source table:** the name of the table that contains the affected record (if there is one).
+  * **Record ID:** if there was one, the ID of the record in the database that was affected by the event.
+  * **Extra information:** detailed information about what happened in the event in JSON format. Not always provided.
+  * **Store name:** the name of the store that the event occurred in.
 Buttons in the window:
@@ Line 14: / Line 25: @@
   * **OK** Close the window.
-<WRAP center round tip 60%>
+**Double-clicking a log entry** in the list will bring up a read-only window showing the full log details:
-Double-clicking a log entry will bring up a small window with the full item details. You can not edit this information.
-</WRAP>
+{{ :admin:pasted:20230124-092633.png?450 |}}
+  * **Date:** The date the log entry was created
+  * **Time:** The time the log entry was created
+  * **User:** The name of the user whoi did the action that resulted in the log entry
+  * **Log ID:** The ID of thelog entry in the database
+  * **Record ID:** The ID of the record the log entry relates to e.g. the transaction that was edited
+  * **Copy ID to Clipboard button:** On click, copies the Record ID value to the Clipboard so you can poaste it somewhere else
+  * **Event type:** The type of the event that occurred. Used for filtering
+  * **Event:** Description of the event that occurred
+  * **View Data button:** On click, if the log entry has additional JSON information, it is displayed in the large panel below the button.
 ==== Dates ====
@@ Line 28: / Line 50: @@
 {{ :admin:log_ddl_2.jpg }}
-See [[.:tables_fields:foreign_keys|this section]] for a complete description of which events are recorded in the log.
 ==== Custom query ====
-If you are looking for log records that are not in the list of common event types described above, you will need to create a custom query.  For example, to find a report of all the finalized POs:
+If you are looking for log records that are not in the list of common event types described above, you will need to create a custom query.  For example, to find a report of all the finalized POs this year:
   - Set the date / time period
@@ Line 42: / Line 63: @@
   - Once you are happy with the included results, click on **Print** (or **Export** to produce a text file that can be imported to Excel and manipulated)
-{{ :admin:2018-10-03_10_38_15_log_query.png |}}
+{{ :admin:2018-10-03_10_38_15_log_query.png?650 |}}
+\\
+\\
+|  //  Previous:  **[[admin:printer_installation]]** | | Next: **[[admin:server_troubleshooting]]** //  |
-// Previous: [[admin:printer_installation|Printer Installation]]     Next: [[admin:server_troubleshooting|Server Troubleshooting]]//
 ---- struct data ----
+pagestatus.status    :
 ----