---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# System log

# System log {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

View warnings and errors for instance processes, records, and non-critical events, such as memory usage on the server machine.{#r_SystemLogs__system-logs-desc}
The following information is tracked in the system log:  
* Workflows
* Configuration
* Chats sessions
* Transactions for each view of each page in the system, including load times for network, server, and browser
* Inbound and outbound email
* Events triggered in the system
* Imports and integrations
* System warnings, errors, and script logs
* Upgrade information for any plugin activations, update sets, or system upgrades
{#r_SystemLogs__ul_kws_csj_sq}

Log entries appear for the current day only. To view other log files, use the log file
browser. This log provides the following information for all occurrences:  
{#r_SystemLogs__table_mdc_nsk_sq__entry__2}

| Field | Description |
|-|-|
| Created | Date and time of the logging activity for the locale of the machine running the instance. |
| Level | Type of message. The levels are Debug, Error, Warning, and Information. * A warning is an error that has been handled and recovered. * An error is something that must be fixed. {#r_SystemLogs__ul_cbp_4jk_znb} |
| Message | System-generated message regarding the nature of the occurrence. Hinweis: Long messages and stack traces are collapsed by default and can be expanded. To disable, see [Disable stack trace formatting in system logs](https://servicenow-prod.fluidtopics.net/TwtS_OsTwt0Pg1slbNyI8g "Enable viewing original unformatted log messages by disabling the collapsible stack trace formatting in system logs."). |
| Source | Name of the process or area affected by the occurrence. For example, the source of the occurrence might be EMAIL or Memory. |
| Source Package | Name of the application package associated with the occurrence. Click on the name to view the Store Application \[sys_store_app\] record for this package. |
[Tabelle : 1. System log]

{#r_SystemLogs__table_mdc_nsk_sq}

## Workflow logging {#r_SystemLogs__section_ugw_kpg_l1b}

* Each activity executed, including:
  * Date and time started
  * Date and time ended
  * State, for example, Finished, Cancelled, Timed Out, Error
  * Result
  * Fault description, if there was an error
  {#r_SystemLogs__ul_xyw_y5j_sq}
* Transition history, including:
  * Time of transition
  * Activity transitioned from
  * Activity transitioned to
  * Which transition was triggered
  {#r_SystemLogs__ul_wkb_dvj_sq}
* Workflow log, including any log statements added to the workflow
{#r_SystemLogs__ul_m1b_xsj_sq}

## Configuration information {#r_SystemLogs__section_rqr_mpg_l1b}

* Action taken, including insert, update, and delete
* Category of change
* Comments recorded with the change
* Name of the change
* XML difference of the change
* Update set the change is associated to
* Date and time of the change
* User who made the change
* Table where the change was made
* Name of the object being changed
* Type of object being changed
* View the change was made in, for changes to forms or lists
{#r_SystemLogs__ul_qwj_4vj_sq}