<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Set up for tracing on Grafana Labs</title><link>https://grafana.com/docs/tempo/v2.10.x/set-up-for-tracing/</link><description>Recent content in Set up for tracing on Grafana Labs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/docs/tempo/v2.10.x/set-up-for-tracing/index.xml" rel="self" type="application/rss+xml"/><item><title>Set up Tempo</title><link>https://grafana.com/docs/tempo/v2.10.x/set-up-for-tracing/setup-tempo/</link><pubDate>Thu, 09 Apr 2026 14:59:14 +0000</pubDate><guid>https://grafana.com/docs/tempo/v2.10.x/set-up-for-tracing/setup-tempo/</guid><content><![CDATA[&lt;h1 id=&#34;set-up-tempo&#34;&gt;Set up Tempo&lt;/h1&gt;
&lt;p&gt;To set up Tempo, you need to:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Plan your deployment&lt;/li&gt;
&lt;li&gt;Deploy Tempo&lt;/li&gt;
&lt;li&gt;Test your installation&lt;/li&gt;
&lt;li&gt;(Optional) Configure Tempo services&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;plan-your-deployment&#34;&gt;Plan your deployment&lt;/h2&gt;
&lt;p&gt;How you choose to deploy Tempo depends upon your tracing needs.
Tempo has two deployment modes: monolithic or microservices.&lt;/p&gt;
&lt;p&gt;Refer to 
    &lt;a href=&#34;/docs/tempo/v2.10.x/set-up-for-tracing/setup-tempo/plan/&#34;&gt;Plan your deployment&lt;/a&gt; to determine the best method to deploy Tempo.&lt;/p&gt;
&lt;h2 id=&#34;deploy-tempo&#34;&gt;Deploy Tempo&lt;/h2&gt;
&lt;p&gt;Once you have decided the best method, you can deploy and set up Tempo.&lt;/p&gt;
&lt;p&gt;Grafana Tempo is available as a &lt;a href=&#34;https://github.com/grafana/tempo/releases&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;pre-compiled binary, OS-specific packaging&lt;/a&gt;, and &lt;a href=&#34;https://github.com/grafana/tempo/tree/main/example/docker-compose&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Docker image&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Refer to 
    &lt;a href=&#34;/docs/tempo/v2.10.x/set-up-for-tracing/setup-tempo/deploy/&#34;&gt;Deploy Tempo&lt;/a&gt; for instructions for deploying using Kubernetes and deploying locally.&lt;/p&gt;
&lt;h2 id=&#34;test-your-installation&#34;&gt;Test your installation&lt;/h2&gt;
&lt;p&gt;Once Tempo is deployed, you can validate Tempo by visualizing traces data:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Using a 
    &lt;a href=&#34;/docs/tempo/v2.10.x/set-up-for-tracing/setup-tempo/test/set-up-test-app/&#34;&gt;test application for a Tempo cluster&lt;/a&gt; for the Kubernetes with Tanka setup&lt;/li&gt;
&lt;li&gt;Using a 
    &lt;a href=&#34;/docs/tempo/v2.10.x/set-up-for-tracing/setup-tempo/test/test-monolithic-local/&#34;&gt;Docker example&lt;/a&gt; to test the Linux setup&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These visualizations test Kubernetes with Tanka and Linux procedures.
They don&amp;rsquo;t check optional configuration you have enabled.&lt;/p&gt;
&lt;h2 id=&#34;optional-configure-tempo-services&#34;&gt;(Optional) Configure Tempo services&lt;/h2&gt;
&lt;p&gt;Explore features by learning about 
    &lt;a href=&#34;/docs/tempo/v2.10.x/configuration/&#34;&gt;available features and configurations&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If you would like to see a simplified, annotated example configuration for Tempo, the &lt;a href=&#34;https://github.com/grafana/intro-to-mltp&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Introduction To MLT&lt;/a&gt; example repository contains a &lt;a href=&#34;https://github.com/grafana/intro-to-mlt/blob/main/tempo/tempo.yaml&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;configuration&lt;/a&gt; for a monolithic instance.&lt;/p&gt;
]]></content><description>&lt;h1 id="set-up-tempo">Set up Tempo&lt;/h1>
&lt;p>To set up Tempo, you need to:&lt;/p>
&lt;ol>
&lt;li>Plan your deployment&lt;/li>
&lt;li>Deploy Tempo&lt;/li>
&lt;li>Test your installation&lt;/li>
&lt;li>(Optional) Configure Tempo services&lt;/li>
&lt;/ol>
&lt;h2 id="plan-your-deployment">Plan your deployment&lt;/h2>
&lt;p>How you choose to deploy Tempo depends upon your tracing needs.
Tempo has two deployment modes: monolithic or microservices.&lt;/p></description></item><item><title>Instrument for distributed tracing</title><link>https://grafana.com/docs/tempo/v2.10.x/set-up-for-tracing/instrument-send/</link><pubDate>Thu, 09 Apr 2026 14:59:14 +0000</pubDate><guid>https://grafana.com/docs/tempo/v2.10.x/set-up-for-tracing/instrument-send/</guid><content><![CDATA[&lt;h1 id=&#34;instrument-for-distributed-tracing&#34;&gt;Instrument for distributed tracing&lt;/h1&gt;
&lt;p&gt;Client instrumentation is the first building block to a functioning distributed tracing visualization pipeline.
Instrumentation handles how traces are generated.
To learn more about instrumentation, refer to &lt;a href=&#34;./about-instrumentation/&#34;&gt;About instrumentation&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Instrumentation is the act of modifying the source code of a service to emit span information tied to a common trace ID.
Traces themselves are a meta-object, comprised of nothing but spans that hold the same ID.&lt;/p&gt;
&lt;p&gt;To instrument your application or service, you need to:&lt;/p&gt;
&lt;!--Commented out - this page has draft:true in the frontmatter. 1. [Choose an instrumentation method to use with your application](./choose-instrumentation-method/)--&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&#34;./set-up-instrumentation/&#34;&gt;Set up instrumentation&lt;/a&gt; to generate traces&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./set-up-collector/&#34;&gt;Set up a collector&lt;/a&gt; to receive traces from your application&lt;/li&gt;
&lt;/ol&gt;
]]></content><description>&lt;h1 id="instrument-for-distributed-tracing">Instrument for distributed tracing&lt;/h1>
&lt;p>Client instrumentation is the first building block to a functioning distributed tracing visualization pipeline.
Instrumentation handles how traces are generated.
To learn more about instrumentation, refer to &lt;a href="./about-instrumentation/">About instrumentation&lt;/a>.&lt;/p></description></item></channel></rss>