> 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/command-centre-diagnostic-logs-unfilte.md).

# Unfiltered Activity Report (Video)

[Command Centre - Diagnostic Logs](/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs.md) › Unfiltered Activity Report (Video)

A video walkthrough of generating an unfiltered activity report for fault finding.

* [Unfiltered Activity Report (video)](https://www.youtube.com/watch?v=KZqtgTQdZqA)

## Activity Report

Where possible, gather an **Activity Report in TEXT format** from Configuration Client, covering 30 minutes before and after the event. Filter by time only, to get all information during the period the issue happened.

The Configuration Client text format is preferred because:

* It contains more information than Command Centre Client reports, and is much easier to search.
* Each event has **two timestamps**: the first column is the event occurrence time, the second is when the server received the event.
* The text report is ordered by event creation time (not by when the event was logged by Command Centre).

Events can appear out of order in a Command Centre Client event report if there are network delays between the controller and the server (network congestion, or failure, where the controller stores events until it runs out of space or the connection is restored).


---

# 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/command-centre-diagnostic-logs-unfilte.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.