---
title: "Discussion on \"Distributed Tracing for a Go Service: One Request, One Thread You Can Pull\" | Hashnode"
description: "Discussion on \"Distributed Tracing for a Go Service: One Request, One Thread You Can Pull\". A payment felt slow and my logs couldn't tell me why. This week I gave the ledger a way to follow a single request from the HTTP handler all the way down to the SQL query."
url: "https://hashnode.com/posts/distributed-tracing-for-a-go-service/6a4c90dc831dfa7583cf0312"
---

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

Discussion

# [Distributed Tracing for a Go Service: One Request, One Thread You Can Pull](https://notes.sohag.pro/distributed-tracing-for-a-go-service?utm_source=hashnode&utm_medium=feed)

A payment felt slow and my logs couldn't tell me why. This week I gave the ledger a way to follow a single request from the HTTP handler all the way down to the SQL query.

Jul 7 · 8 min read · notes.sohag.pro  
Read the article

-   [#go](https://hashnode.com/tag/go)
-   [#golang](https://hashnode.com/tag/golang)
-   [#opentelemetry](https://hashnode.com/tag/opentelemetry)
-   [#observability](https://hashnode.com/tag/observability)
-   [#tracing](https://hashnode.com/tag/tracing)

## Written by

[Sohag Hasan](https://hashnode.com/@sohag)

@sohag · Dhaka, Bangladesh

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

Tech Lead at MobyPay | Certified Laravel Developer | PHP JS GO | DevOps Enthusiast | Open to projects

WhoAmI => notes.sohag.pro/author

## Responses

Markdown supported · ⌘↵ to post

No responses yet.