---
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


---

# View a historical domain message

# View a historical domain message {#ariaid-title1}

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

View historical domain messages in the log file to troubleshoot domain separation issues.

## Vorbereitungen

Role required: admin

## Prozedur

1. Enable verbose domain logging: Navigate to AllDomain AdminDomain Separation CenterConfigure Domain CenterEnables detail domain loggingYes (or set property `glide.sys.domain.verbose` to True).
2. Navigate to System DiagnosticsSession DebugEnable All.
3. Let the debug session run for a time period, such as a day, before checking the log files.
4. Navigate to System LogsUtilitiesNode Log File Download.
5. Open the record for the day you want to view.  
   Log files use the naming format `localhost_log.<yyyy-mm-dd>.txt`.
6. Click the Download log related link.
7. Open the downloaded log file in a text editor and search for log messages with the following format:  
   Query against table incident restricted by domain values `[global,
   Software[8a4dde73c6112278017a6a4baf547aa7]]`

   In this example, a user only saw records from the Incident table that matched
   the global and Software domains.
{#t_ViewAHistoricalDomainMessage__steps_gbf_kd3_1r}