> For the complete documentation index, see [llms.txt](https://docs.xrpl-commons.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xrpl-commons.org/core-dev-bootcamp/module02/homeworks/homework3.md).

# Homework 3: Logging and Debugging

[← Back to Rippled II Overview](/core-dev-bootcamp/module02.md)

***

### Objective

Configure logging and analyze Rippled's internal behavior.

**Format**: Written report (PDF or Markdown) with screenshots/code snippets

#### Requirements

1. **Enable Detailed Logging**
   * Enable trace-level logging for the Transaction partition
   * Submit a transaction
   * Capture the relevant log output
2. **Log Analysis**
   * Identify and explain 5 key log messages related to transaction processing
   * For each log message, explain:
     * What subsystem generated it
     * What phase of processing it represents
     * What information it provides to developers

#### Deliverable

A report containing:

* Commands used to enable logging
* Log excerpts (formatted properly)
* Analysis of 5 log messages with explanations


---

# 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://docs.xrpl-commons.org/core-dev-bootcamp/module02/homeworks/homework3.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.