> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs/using-cmtrace-exe-to-view-logs.md).

# Using CMtrace.exe to view logs

[Command Centre - Diagnostic Logs](/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs.md) › Using CMtrace.exe to view logs

`CMtrace.exe` is a free Microsoft tool bundled with System Center Configuration Manager (SCCM), but it can be used independently and is far better than Notepad for reading Command Centre logs.

**Download:** From [security.gallagher.com/downloads](https://security.gallagher.com/downloads) under **Third Party Software & Drivers → Microsoft**.

## Real-time monitoring

CMtrace monitors changes to a log file and displays updates in real-time, with a pause button for when the log updates too quickly. There is no need to close and re-open log files to see the latest content.

## Automatic highlight of errors and warnings

By default, errors are highlighted in red and warnings in yellow, which helps spot problems in a long list of messages.

![CMtrace log view with error lines highlighted red and warning lines highlighted yellow](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2024b2469cf9ab4e500566f54da05b9e2f3527e2%2FSECHUB-CCS-DIAG-cmtrace-auto-highlight.png?alt=media)

## Custom highlight of keywords

CMtrace can highlight lines containing a word or phrase. By default it uses the same yellow as warnings, so choose a different, easily identifiable colour first via **File → Preferences**.

![CMtrace File menu and Preferences dialog, with the highlight colour picker indicated](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-a36a22fb72d4da244c69f0fd11e9b7b96458fd50%2FSECHUB-CCS-DIAG-cmtrace-preferences-highlight.png?alt=media)

Then go to **Tools → Highlight** and type a word or phrase.

![CMtrace Highlight dialog with the phrase "INVITE sip" entered](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-f8784fcf6099a2a285281c5e1be1b14f96b1af32%2FSECHUB-CCS-DIAG-cmtrace-highlight-dialog.png?alt=media)

Any line containing the phrase is highlighted, which is useful when troubleshooting SIP logs, for example.

![CMtrace log view with lines containing "INVITE sip" highlighted in pink](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-9a6633e0394ba106964b83b65c7e71b7ccad11d1%2FSECHUB-CCS-DIAG-cmtrace-custom-highlight-result.png?alt=media)

## Filtering by keywords

CMtrace can show only the lines that match a filter, via **Tools → Filter**. The most useful option is "contains". In Command Centre logs, entries carry thread information, so you can filter out the noise from other threads.

![CMtrace log before filtering, with a thread identifier highlighted among many other entries](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-14acb757d3a467c9fef982144b875b33b01ce322%2FSECHUB-CCS-DIAG-cmtrace-before-filter.png?alt=media)

![CMtrace Filter Settings dialog set to "Filter when the Entry Text contains \[16c4:1ccc\]"](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fa92898715422fc16ac3891d1ee3cc100e025288%2FSECHUB-CCS-DIAG-cmtrace-filter-dialog.png?alt=media)

In the example below, filtering on the entry text containing `[16c4:1ccc]` follows a single process and jumps from 18:00 to 18:13, skipping 13 minutes of noise from other processes.

![CMtrace log after filtering, showing only the entries for the single filtered thread](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-03d48821c50b3e823c4101511ac9984d3158d877%2FSECHUB-CCS-DIAG-cmtrace-after-filter.png?alt=media)

> **Note:** The Component, Thread and Time filter fields expect the log to be consumed from an SCCM server, so only the **Entry Text** field is useful when using CMtrace as a standalone tool.

## Ease and portability

`CMtrace.exe` is under 800 KB and needs no installation. Double-click it and use **File → Open** (Ctrl+O) to open a log. You can associate `.log` files with CMtrace. If you intend to use it long term, store it somewhere permanent. For multi-user access, avoid `C:\Users\...` folders (Downloads, Desktop, Documents), and store it in `C:\Windows` or a custom folder like `C:\Tools`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs/using-cmtrace-exe-to-view-logs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.