> For the complete documentation index, see [llms.txt](https://copilot-docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://copilot-docs.bugbase.ai/enterprise/activity/logging.md).

# Logging

Logs record scan and system events that are useful for troubleshooting. They are separate from final findings: a scan can produce useful logs even when it produces no vulnerabilities.

## When to Use Attack Logs

Use **Activity -> Attack Logs** when:

* a module or submodule failed;
* a scan is stuck or slower than expected;
* a browser session stopped working;
* a target blocked or rate-limited requests;
* an internal agent disconnected;
* an internal host or service was unreachable;
* a scheduled run did not start;
* you need scan evidence for review or escalation.

## What to Look For

| Symptom                | Log evidence to check                                                                         |
| ---------------------- | --------------------------------------------------------------------------------------------- |
| Browser session failed | validation errors, replay failures, expired auth, missing storage, verification URL mismatch. |
| Target blocked scanner | HTTP 403/429 patterns, WAF pages, captcha loops, rate-limit calibration failures.             |
| Internal agent issue   | disconnects, heartbeat gaps, job pickup failures, route or interface errors.                  |
| Module timeout         | max runtime cancellation, submodule timeout, long-running job status.                         |
| Queue delay            | scheduled/running state with delayed worker pickup.                                           |

## Filtering

Filter logs by time range, module, severity, and text search. Start with the module reference from **Activity -> Activity**, then narrow to the failing time window.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://copilot-docs.bugbase.ai/enterprise/activity/logging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.