> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/components-and-data/agents/agent-details/logs/session-log.md).
# Session Log
In terms of agent-type, a session can be defined as follows:
* Http to Flow Agent — A session represents the execution of the flow in response to a single HTTP request.
* Event to Flow Agent — A session represents the execution of the flow with respect to the processing of a single message received from the messaging service.
By clicking on the "session ID" for a specific log session, the messages from that log session are displayed:
Each log message is a JSON object at the root level, such that if there are 10 messages in the sesion, then there will be 10 nodes under the "root" (session).
The first level of properties of the message represent the various context properties that contain information about the agent and session.
The "message" property contains the results of a log-tap or debug node within the flow. Properties on the message include:
* id: The ID of the log-tap or debug node
* name: The name of the log-tap or debug node
* type: The type of the node (e.g. "log-tap")
* message: The specific message output by the node
The message property can be expanded to show the details of the log message. Of course the contents of that message are dependent on the specific configuration of the log-tap or debug node.
The "collapse controls" at the top of the window allow you to expand or collapse the entire session log to a specified level.
---
# 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.contextual.io/documentation-and-resources/components-and-data/agents/agent-details/logs/session-log.md?ask=&goal=
```
`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.