> 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/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-logs.md).

# REST API - logs

Configure and interpret Command Centre REST API request logging.

Command Centre can log REST activity through registry keys on the server. The main log is `C:\ProgramData\Gallagher\Command Centre\Command_centre.log` (with trace enabled).

The registry keys live under `HKLM\SOFTWARE\Gallagher\Command Centre` (on 64-bit, `HKLM\SOFTWARE\WOW6432Node\Gallagher\Command Centre`). For **vEL8.00 and earlier**, use `HKLM\SOFTWARE\Cardax\Command Centre FT`.

| Key (DWORD)           | Values                                                                                             | Purpose                                                                                                                                                                                                                                                                                                   |
| --------------------- | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `LogRESTRequests`     | 0 (if missing); 1 (set by the 8.90 installer if missing)                                           | **vEL8.90+** (and a special 8.70 branch): all public-API calls are written to `RESTAccess.log` in the same directory as the main log. Obsoletes `LogRESTSourceIP` (but does not log the client certificate CN). Each line is strict JSON. You may add to it (keep it small); do not change what is there. |
| `LogRESTSourceIP`     | —                                                                                                  | **vEL8.60 MR3+, 8.70 MR2+, 8.80**: logs the source IPs of REST callers into the Command Centre log (plus the remote client certificate CN, if used). **Removed in 8.90** (obsoleted by `LogRESTRequests`).                                                                                                |
| `LogRESTURLMaxLength` | 200 (default and if missing; set by the 9.00 installer); `0` omits all URLs; `8192` is the maximum | **vEL9.00**: limits the URL length recorded in the REST access logs.                                                                                                                                                                                                                                      |

***

🔗 **Related**

* [REST API - Connection](/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-connection.md). The alarms these logs support.


---

# 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/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-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.