Grafana says Unable to connect to Tempo search after fresh install

  • What Grafana version and what operating system are you using?
    v9.5.3
    Ubuntu Server

  • What are you trying to achieve?
    Searching data with Tempo via the Grafana UI

  • How are you trying to achieve it?
    I am trying to explore data with Tempo inside of the Grafana UI

  • What happened?
    When I click on the search tab in the Tempo datasource screen, it has a notification that says:

Unable to connect to Tempo search

  • What did you expect to happen?
    Be able to search without the notification

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

Unable to connect to Tempo search

Please ensure that Tempo is configured with search enabled. If you would like to hide this tab, you can configure it in the [datasource settings].

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

Hi,

I also ran into this issue, could you please let me know the resolution.

So far, no solution found on my end. I will keep trying and if I find something I will let you know.

** UPDATE - Marking this as the solution. Once I did this change I was able to search tempo data.

Alright,

I’ve been looking around and just happen to find something that seems to have fixed that message.

Try adding the following to your tempo config yaml

search_enabled: true

I will do more testing to confirm before I set this as the solution. Let me know if that fixes you too.

1 Like

Thank you, search_enabled setting worked. But i didn’t see this setting in grafana documentation .
one more point thought of sharing with you, when i build tempo from source code , i didn’t face this issue.

Turns out the documentation for setting up Tempo on Linux is incorrect. It uses Tempo 1.5 and in version 2.0 they’ve removed that search_enable: true requirement.

That would explain why building from source you don’t need it but installing it via the installation instructions requires. it.

I’ve contacted their documentation team and they will be updating that.