> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/mcp/tools/logger-messages.md).

# loggerMessages

Read buffered real-time log messages from an active logger session. Returns parsed and structured log entries. Call repeatedly to poll for new messages.

Must be called after `loggerStart`.

### Parameters

| Parameter     | Type   | Required | Description                                       |
| ------------- | ------ | -------- | ------------------------------------------------- |
| `maxMessages` | number | No       | Maximum messages to return (1-1000). Default: 50. |

### Output

Returns structured log entries, each containing:

* **method** - HTTP method (GET/POST)
* **eventName** - The event name (PageView, Purchase, etc.)
* **path** - API endpoint path
* **timestamp** - When the event occurred
* **outcome** - Success or exception
* **exceptions** - Error details (if any)
* **meta** - Event metadata including params, payload, user properties, consent, and host data
* **channels** - Per-channel delivery details including requests sent and responses received

### Example

> "Show me the latest log messages"

The AI assistant will call `loggerMessages` and display the recent events with their delivery status across channels.


---

# 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.edgetag.io/mcp/tools/logger-messages.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.