--- title: Log details panel description: Inspect a single log in Explore, filter by its field values, view surrounding and related logs, and open linked traces and resources. url: https://coralogix.com/docs/user-guides/data_exploration/logs/info_panel/ product: data-exploration feature: Logs Explorer feature_id: logs-explorer feature_identifier: data-exploration/logs-explorer last_updated: '2026-11-12' --- # Log details panel The log details panel opens when you select a log entry in the Explore results table. It displays the full record for the selected log, including its fields and related observability data. Use the log details panel to inspect a single event in depth, filter your investigation based on specific field values, and navigate to related logs, traces, and metrics. ## Use cases * Review the full field set of a log entry without switching screens. * Filter the Explore results to include or exclude specific field values found in a log. * Correlate a log event with its associated trace, span, or resource metrics. * Understand the context of an error by viewing surrounding log entries. ## What you need * Access to Explore with at least read permissions for the relevant dataset. * Log data ingested into Coralogix. ## Open the log details panel 1. In **Explore**, run a query to return log results. 2. Select any log row in the results table. The panel opens on the right side of the screen. The selected row is highlighted in the table. [![Log details panel open on the right side of Explore showing the full log entry](/docs/assets/images/logs-info-panel-a4165653c8810bed606afb0fe4b85b5c.webp)](https://coralogix.com/docs/assets/images/logs-info-panel-a4165653c8810bed606afb0fe4b85b5c.webp) To close the panel, select the **X**, select the same row again to toggle it off, or select a column header, the toolbar, or an empty area of the grid. To keep the panel open while browsing results, use the navigation arrows within the panel to move between log entries. When you arrive in Explore from a [Deep link](https://coralogix.com/docs/user-guides/data_exploration/deep-links.md) that targets a specific log, the info panel opens automatically, even if that log isn't in the current grid (for example, because the query has changed since the link was created). If the log can no longer be loaded, the panel shows a **Log not found** empty state instead of the record. ## Resize the panel Select **Expand to full width** in the panel header to maximize the panel across the viewport when you need more room to read a structured log or compare fields. Select **Exit full width** to return to the default width. The same toggle is available on the Templates info panel. ## Log context and labels The panel header shows the log's context as compact visual elements rather than labeled rows: * A color-coded **severity badge** indicates the log severity level (for example, Error, Warning, Info). * The **timestamp** appears as a formatted string next to the badge. * **Application** and **Subsystem** appear as `key = value` chips. Each chip is a single button that opens the [field context menu](https://coralogix.com/docs/user-guides/data_exploration/logs/grid.md#field-context-menu) (see [Row actions](#row-actions)). * A **Trace ID chip** appears when the log carries a trace ID. Select it to open the span drawer for that trace. * A **Template ID chip** appears when the log belongs to a [template](https://coralogix.com/docs/user-guides/data_exploration/logs/templates.md). Select it to open the Templates info panel. ## Tabs in the panel The panel has three tabs below the header: * **Log**: the full record view, with the log message and field list. * **Related Logs**: finds logs with similar attributes around the same time. Pick which attributes to match. * **Resources**: infrastructure attributes and resource metric charts for the log's host or service. If the log doesn't carry infrastructure context, the tab shows an empty state. ## View surrounding logs Select **View surrounding logs** in the panel header to open the **Customize surrounding logs** dialog, where you scope the search and set the time window before loading results. [![The Customize surrounding logs dialog in the log details panel, showing the Filter your search query and the Select time range controls](/docs/assets/images/info-panel-surrounding-logs-f9ce9c257261120b88e6287bcca0c594.webp)](https://coralogix.com/docs/assets/images/info-panel-surrounding-logs-f9ce9c257261120b88e6287bcca0c594.webp) The dialog has two parts: * **Filter your search**: the query that scopes which logs count as surrounding. It defaults to the selected log's application and subsystem (`$l.applicationname:"…" AND $l.subsystemname:"…"`). Edit the query to add or change fields; the field offers autocomplete. * **Select time range**: how much context to load before and after the selected log. For each side, choose a duration (**5 Seconds**, **30 Seconds**, **1 Minute**, **5 Minutes**, **10 Minutes**) or a number of logs (**10 Logs**, **30 Logs**, **50 Logs**). You set this window once in the Log Details panel, and it applies to the surrounding-logs action everywhere, including the logs grid. Select **Apply** to load the results. Coralogix opens the surrounding logs in a separate Explore tab. The original log stays marked and highlighted, with an indicator of how many logs loaded before and after it and the time range covered. The cap is 100 logs total, up to 50 on each side, whatever window you choose; the time range only controls how far Coralogix looks. The logs grid offers the same action from its [row actions](https://coralogix.com/docs/user-guides/data_exploration/logs/grid.md#row-actions) menu, using the window you set here. ## Log tab The **Log** tab shows the log message and field list with three view modes: * **Table**: fields rendered as rows of key/value pairs. Use the **Search table** field to filter the visible rows; matching text is highlighted. * **JSON**: the log rendered as formatted JSON. * **Raw**: the unprocessed raw message text. [![Log tab showing log attributes in Table, JSON, and Raw view formats](/docs/assets/images/info-panel-log-message-3d6cf7a9139c2e9c3f2f7f64fae73d0e.webp)](https://coralogix.com/docs/assets/images/info-panel-log-message-3d6cf7a9139c2e9c3f2f7f64fae73d0e.webp) The **Message** section is pinned at the top of the tab. Use **Show more** / **Show less** to expand truncated messages. A more-actions () menu in the message header offers **Copy**, **Filter by**, and **Exclude**. To filter on part of a message, highlight the text you want and select **Add to filter**. Coralogix filters on that substring wherever it appears. See [Field context menu](https://coralogix.com/docs/user-guides/data_exploration/logs/grid.md#field-context-menu) for the full behavior. ## View metadata fields The **Log** tab's **Table** view lists the log's parsed body fields (for example, `Message`, `LogLevel`, and `Scopes.*`), it doesn't break out the Coralogix metadata namespace (`$m`, stored under `coralogix.metadata.*` paths) as key/value rows. The metadata is present in the **JSON** and **Raw** views, but only nested inside the raw record's `metadata` object, so reading a specific field there means parsing the raw body by hand. A few metadata values also appear in the panel header, severity, timestamp, and template (see [Log context and labels](#log-context-and-labels)). To read a metadata field as a clean, usable value, use one of these approaches: * **Add metadata as columns.** Select **Columns** in the Logs tab header, search for `coralogix.` to list the metadata fields, and add the ones you want as columns. See [Columns](https://coralogix.com/docs/user-guides/data_exploration/logs/grid.md#columns) for full column management. The [Fields panel](https://coralogix.com/docs/user-guides/data_exploration/fields.md#sections-on-the-logs-dataset) lists these metadata fields too. * **Query metadata with DataPrime.** Use the `$m.` access mechanism to read and inspect metadata programmatically. The most reliable way to work with these fields. See [Access mechanisms](https://coralogix.com/docs/dataprime/language-reference/access_mechanisms.md) for the `$m` schema and the list of available keys. ## Row actions The **Table** view lists each field as a `key` / `value` row. Selecting the key or the value opens the same [field context menu](https://coralogix.com/docs/user-guides/data_exploration/logs/grid.md#field-context-menu) the logs table uses, narrowed to what you selected. A key offers the field-level actions: **Exists** / **Not Exists**, **Add as a column**, **Group by**, **Add to favorite fields**, and **Show distribution**. A value offers the actions that act on it, such as **Filter by** / **Add to filter**, **Exclude**, **Replace filter with**, **Value across time**, and **Copy key:value**. **Copy value** and **Custom Actions** appear for both. Value actions that depend on context surface only where they apply: **Service drilldown** on service fields, **View in RUM Sessions** on the `rum.events` dataset, and **Live tail** on **Application** and **Subsystem** values. The same menu opens from the **Application** and **Subsystem** chips in the panel header. Each chip is a single button. Select anywhere on it to open the menu. ## Related logs tab The **Related Logs** tab surfaces logs with similar attributes around the same time. Pick which attributes to match (for example, application, subsystem, host) to scope the search. Use this tab to widen the lens from a single log to its neighborhood without leaving the panel. ## Resources tab The **Resources** tab shows infrastructure attributes and resource metric charts for the host or service associated with the log. Use it to confirm whether an error coincided with resource exhaustion, container restarts, or other infrastructure events. If Coralogix doesn't detect any infrastructure context for the log, the tab shows an empty state ("We didn't find infrastructure attributes or metrics for this log"). ## Send the log to Olly as data context Select **Add to Olly context** in the panel header to open the Olly chat with this log attached as a data-context chip. Use it to ask Olly about the exact log, for example to explain an unfamiliar format, error code, or message. [![The log details panel header with the Add to Olly context button highlighted and its tooltip showing](/docs/assets/images/info-panel-add-to-olly-context-1e28d059bea5ad4b759174ba82bbae04.webp)](https://coralogix.com/docs/assets/images/info-panel-add-to-olly-context-1e28d059bea5ad4b759174ba82bbae04.webp) Olly groups the objects you pin into a chip per type in the prompt; hover the **Logs** chip to see each pinned log, whose tooltip reads **Log: \**. You can add more logs from the [Logs table](https://coralogix.com/docs/user-guides/data_exploration/logs/grid.md#add-a-log-to-olly-context) or spans from the tracing drilldown. See [Page and data context](https://coralogix.com/docs/user-guides/olly/olly-chat.md#page-and-data-context) for chip behavior. ## Share the panel state Select the **Share URL** link icon in the panel header to copy a shareable URL that recreates the current query, time range, and selected log. ## Navigate between logs Use the navigation controls at the top of the panel to move between log entries without closing the panel: * Select the up arrow (tooltip **Previous Log**) to move to the previous log entry in the results table. * Select the down arrow (tooltip **Next Log**) to move to the next log entry. The results table scrolls to keep the selected row visible as you navigate. ## Next steps Switch from raw rows to aggregated views in the [Overview tab](https://coralogix.com/docs/user-guides/data_exploration/overview-tab.md).