Explore panel logs are stacked on each other

Grafana Explore
1

My environment:

  • Grafana 13.0.1
  • Kubernetes 1.35.2
  • Chrome 149.0.7827.103

This is a new deployment, and when exploring the logs, the entries appear to stack on top of each other. I can clear it with a browser refresh, but when I run another query, it reverts to a jumbled mess.

I currently have line wrap disabled, the smaller font, and deduplication is set to none.

Here is what it looks like.

Cleanshot_2026-06-17_16.21.24
Cleanshot_2026-06-17_16.21.241369×574 249 KB

Is this a known Chrome issue? Are there any suggestions that anyone can provide? It gets annoying fast.

Thanks!

2

Try enabling Wrap lines → as per official Grafana documentation

this wraps long lines to fit within the visible width of the viewer and can fix the stacking display issue.

Screenshot (683)
Screenshot (683)1920×561 234 KB

when i use wrap lines enabled the logs are stacking differently
Screenshot (684)
Screenshot (684)1920×561 193 KB

In Grafana 13 this option is found here:

Explore → Logs panel → right side options
→ Click "Wrap JSON" dropdown
→ Select "Enable line wrapping"

If it still persists, try Firefox or Edge to confirm if Chrome-specific,

3

I had tried using word wrap prior. Tried it again on Chrome and got the same result.

I am currently trying out Zen Browser (Firefox-based), and I get the same results:

Cleanshot_2026-06-19_13.22.00
Cleanshot_2026-06-19_13.22.001504×784 473 KB

My laptop is running MacOS Sequoia v15.7.4 if it matters.

Thanks

5

Which datasource are you using?

6

“Which datasource are you using?”

This strikes me as a question worthwhile adding to the existing list:

  • What Grafana version and what operating system are you using?

  • What are you trying to achieve?

  • How are you trying to achieve it?

  • What happened?

  • What did you expect to happen?

  • Can you copy/paste the configuration(s) that you are having problems with?

  • Did you receive any errors in the Grafana UI or in related logs? If so,
    please tell us exactly what they were.

  • Did you follow any online instructions? If so, what is the URL?

Antony.

7

To anyone experiencing this issue, the root cause was identified to be duplicated IDs in the logs response. This should be addressed in every data source that is sending IDs that are not unique, but we also recently updated the Logs Panel so even in the presence of repeated IDs, it doesn’t affect rendering. Logs Panel: Make virtualization resilient to duplicated UIDs by matyax · Pull Request #130854 · grafana/grafana · GitHub

It’s worth noting that repeated IDs break the contract between the UI and the data source, and cause other unexpected behaviors, as IDs are expected to be unique.