---
title: "Discussion on \"Deploying Tempo Distributed Tracing Backend on Ubuntu 24.04\" | Hashnode"
description: "Discussion on \"Deploying Tempo Distributed Tracing Backend on Ubuntu 24.04\". Step-by-step guide to deploy Grafana Tempo with Docker Compose and Traefik on Ubuntu 24.04, with persistent trace storage and automatic HTTPS for a production-grade distributed tracing backend."
url: "https://hashnode.com/posts/deploying-tempo-distributed-tracing-backend-on-ubuntu-24-04/6a0dbe9bb1ed7bce01e0cf2e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Deploying Tempo Distributed Tracing Backend on Ubuntu 24.04](https://vultr.hashnode.dev/deploying-tempo-distributed-tracing-backend-on-ubuntu-24-04?utm_source=hashnode&utm_medium=feed)

Step-by-step guide to deploy Grafana Tempo with Docker Compose and Traefik on Ubuntu 24.04, with persistent trace storage and automatic HTTPS for a production-grade distributed tracing backend.

May 20 · 3 min read · vultr.hashnode.dev  
Read the article

-   [#docker](https://hashnode.com/tag/docker)
-   [#devops](https://hashnode.com/tag/devops)
-   [#self-hosted](https://hashnode.com/tag/self-hosted)
-   [#ubuntu-2404](https://hashnode.com/tag/ubuntu-2404)
-   [#opensource](https://hashnode.com/tag/opensource)
-   [#observability](https://hashnode.com/tag/observability)

## Written by

[Sanskriti Harmukh](https://hashnode.com/@sharmukh)

@sharmukh · Durg, India

  
[View profile](https://hashnode.com/@sharmukh)

Developer Advocate at Vultr

A Developer Advocate with a focus on improving the developer experience through clear communication, technical enablement, and community engagement.

## Responses 2

Markdown supported · ⌘↵ to post

[jasminepark](https://hashnode.com/@jasmineparkdev)

[May 21](https://hashnode.com/posts/deploying-tempo-distributed-tracing-backend-on-ubuntu-24-04/6a0dbe9bb1ed7bce01e0cf2e/comment/6a0eb1258b0346022103fa69)

Solid step-by-step. One operational note from running Tempo at scale: cardinality on span attributes is the silent killer. We had to pull high-cardinality fields like raw prompt text out of attribute labels and into a separate ClickHouse column with sampling. Query latency dropped from 8s to 200ms. Worth thinking about retention policy early.

[Sanskriti Harmukh](https://hashnode.com/@sharmukh)

[May 21](https://hashnode.com/posts/deploying-tempo-distributed-tracing-backend-on-ubuntu-24-04/6a0dbe9bb1ed7bce01e0cf2e/comment/6a0eb1258b0346022103fa69#reply-6a0ef91e8b03460221466195)

Great operational callout, cardinality is exactly the kind of thing that doesn't bite you until you're at scale. This guide uses local storage and default retention to keep the deploy simple, but you're right that retention policy and attribute cardinality strategy deserve early thought in production setups
