> ## Documentation Index
> Fetch the complete documentation index at: https://metorial.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring and Observability

> Metorial provides monitoring tools to help you understand how your providers are performing and debug issues.

<Note>
  **What you'll learn:**

  * How to view session logs, messages, and events
  * How to debug issues

  **References:**

  * [Monitoring in Dashboard](/review-activity)
  * [Sessions Guide](/concepts-sessions)
</Note>

## Viewing Logs

Access logs for your sessions through the Metorial dashboard:

1. Navigate to your project
2. Select the **Logs** tab

<img src="https://mintcdn.com/metorial/fydw7J6y9LueIJC4/images/metorial-101/monitoring-mcp-servers/step1.png?fit=max&auto=format&n=fydw7J6y9LueIJC4&q=85&s=2932e45c41c9cf1bf2ab56fe17a7f649" alt="Logs tab showing Sessions view" width="3838" height="2046" data-path="images/metorial-101/monitoring-mcp-servers/step1.png" />

### Session Logs

See details for each session:

* Creation timestamp
* Providers attached
* Tool calls made
* Any errors

### Tool Call Details

Expand individual tool calls to see:

* Input parameters
* Response data
* Execution time
* Error messages (if any)

<img src="https://mintcdn.com/metorial/fydw7J6y9LueIJC4/images/metorial-101/monitoring-mcp-servers/step2.png?fit=max&auto=format&n=fydw7J6y9LueIJC4&q=85&s=5f80e959459e18a8cfa7f2feefa698fd" alt="Session detail view with logs" width="3838" height="2046" data-path="images/metorial-101/monitoring-mcp-servers/step2.png" />

## Session Data via API

Sessions expose detailed monitoring data through the API:

### Messages

Every tool call and MCP protocol message is recorded as a **session message**. Each message includes:

* `type`: `tool_call`, `mcp_control`, or `mcp_message`
* `status`: `waiting_for_response`, `succeeded`, or `failed`
* `input` and `output` payloads
* Timing information

### Events

**Session events** capture significant occurrences:

* Connections opening and closing
* Errors
* State changes

### Connections

Each client that connects to a session creates a **connection**. You can inspect connection state (`connected` / `disconnected`), transport type, and usage statistics.

## Debugging Common Issues

### Authentication Errors

* Verify your API key is correct
* Check that provider auth configs exist and haven't expired
* For OAuth providers, the user may need to re-authorize via a new setup session

### Tool Execution Errors

* Verify tool parameters match the schema
* Check for rate limiting from external services
* Review error messages in session logs

<Info>
  **Getting Help**

  If you can't resolve an issue:

  1. **Export relevant logs** from the dashboard
  2. **Note session and provider deployment IDs** for affected sessions
  3. **Contact support** at [support@metorial.com](mailto:support@metorial.com)
</Info>

## What's Next?

<CardGroup cols={2}>
  <Card title="Monitoring Guide" icon="vial" href="/review-activity">
    Learn more about monitoring your providers.
  </Card>

  <Card title="Error Handling" icon="circle-exclamation" href="/sdk-error-handling">
    Handle errors gracefully in your code.
  </Card>
</CardGroup>