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

# Log Panel

> Text log viewer for ROS diagnostic and application messages

The Log panel displays timestamped text log messages from your recording. It renders output from ROS logging topics such as `/rosout` and other diagnostic streams, providing insight into system behavior, warnings, and errors alongside the sensor data.

## Supported Data

| Schema                   | Description          | Typical Topics                       |
| ------------------------ | -------------------- | ------------------------------------ |
| `rosgraph_msgs/Log`      | ROS standard logging | `/rosout`, `/rosout_agg`             |
| `rcl_interfaces/msg/Log` | ROS 2 logging        | `/rosout`                            |
| Log-type messages        | Text log output      | Topics containing `log` or `/rosout` |

### Auto-Detection

A topic is assigned to the Log panel when:

* Its schema is a recognized ROS log message type, **or**
* Its topic name contains `log` or `/rosout` (note the leading slash)

## Features

### Severity Levels

Log messages include a severity level that indicates the importance of the message. The Log panel color-codes messages by severity for quick visual scanning.

| Level     | Description                                     | Display            |
| --------- | ----------------------------------------------- | ------------------ |
| **DEBUG** | Detailed diagnostic information                 | Muted text         |
| **INFO**  | Normal operational messages                     | Standard text      |
| **WARN**  | Potential issues that may need attention        | Yellow highlight   |
| **ERROR** | Errors that prevented an operation              | Red highlight      |
| **FATAL** | Critical failures requiring immediate attention | Bold red highlight |

### Severity Filtering

Filter the log view to show only messages at or above a specific severity level. This helps you focus on important messages in recordings that produce large volumes of debug output.

<Tabs>
  <Tab title="All messages">
    Show every log message regardless of severity. Useful for detailed debugging when you need the full context.
  </Tab>

  <Tab title="Warnings and above">
    Filter to WARN, ERROR, and FATAL messages only. Useful for quickly identifying problems without scrolling through routine messages.
  </Tab>

  <Tab title="Errors only">
    Show only ERROR and FATAL messages. Useful for post-incident analysis when you need to find failures quickly.
  </Tab>
</Tabs>

### Timestamp Correlation

Every log message includes a timestamp that corresponds to the shared timeline used by all panels. This enables direct correlation between log events and sensor data:

* **Click a log entry** to seek the entire viewer to that message's timestamp. Camera images, point clouds, and plots all update to show the state at the moment the log was emitted.
* **Current time indicator** highlights log messages near the current playback position, so you can see what the system was logging at any point in the recording.

### Scrolling Behavior

| Mode              | Behavior                                                                        |
| ----------------- | ------------------------------------------------------------------------------- |
| **Auto-scroll**   | During playback, the log panel scrolls to keep the most recent messages visible |
| **Manual scroll** | When you scroll manually, auto-scroll pauses so you can inspect older messages  |
| **Resume**        | Click the "jump to latest" button to re-enable auto-scroll                      |

## Common Use Cases

<CardGroup cols={2}>
  <Card title="" icon="triangle-exclamation">
    <p style={{fontWeight: 600, fontSize: '18px', marginBottom: '4px', marginTop: '8px', color: 'inherit'}}>Error investigation</p>
    <p style={{fontSize: '14px', marginTop: '0px', opacity: 0.6}}>Filter for errors and correlate log timestamps with sensor data to understand what was happening when a failure occurred.</p>
  </Card>

  <Card title="" icon="heart-pulse">
    <p style={{fontWeight: 600, fontSize: '18px', marginBottom: '4px', marginTop: '8px', color: 'inherit'}}>System health monitoring</p>
    <p style={{fontSize: '14px', marginTop: '0px', opacity: 0.6}}>Review warning and info messages to assess overall system behavior during the recording.</p>
  </Card>

  <Card title="" icon="stethoscope">
    <p style={{fontWeight: 600, fontSize: '18px', marginBottom: '4px', marginTop: '8px', color: 'inherit'}}>Sensor diagnostics</p>
    <p style={{fontSize: '14px', marginTop: '0px', opacity: 0.6}}>Check for sensor driver warnings, timeout messages, or data quality alerts that may affect annotation.</p>
  </Card>

  <Card title="" icon="clock">
    <p style={{fontWeight: 600, fontSize: '18px', marginBottom: '4px', marginTop: '8px', color: 'inherit'}}>Debugging timing issues</p>
    <p style={{fontSize: '14px', marginTop: '0px', opacity: 0.6}}>Use log timestamps to identify timing problems, such as delayed sensor initialization or dropped messages.</p>
  </Card>
</CardGroup>

<Tip>
  When investigating a specific event, click the log entry's timestamp to seek all panels to that moment. This is the fastest way to correlate log output with what the cameras and LiDAR were seeing.
</Tip>

## Related

* [Raw Messages Panel](/docs/visualization/panels/raw-messages-panel) -- Inspect the full structured content of any message
* [Plot Panel](/docs/visualization/panels/plot-panel) -- Numeric data plotted over the same timeline
* [Multi-Sensor Viewer](/docs/visualization/multi-sensor-viewer) -- Overview of the synchronized multi-panel layout