--- title: Error Handling in Go Programs | daily.dev description: Practical patterns for handling errors in Go, based on production experience at Teleport. Covers the pitfall of shadowing original errors by wrapping them with... canonical: https://daily.dev/posts/error-handling-in-go-programs-eq1vi28ks twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Error Handling in Go Programs | daily.dev og:description: Practical patterns for handling errors in Go, based on production experience at Teleport. Covers the pitfall of shadowing original errors by wrapping them with... og:url: https://daily.dev/posts/error-handling-in-go-programs-eq1vi28ks og:image: https://api.daily.dev/og/posts/EQ1VI28Ks.png og:image:alt: Error Handling in Go Programs og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Error Handling in Go Programs **[Teleport](https://daily.dev/sources/teleport)** · 5 min read · 0 upvotes · 0 comments ## Summary Practical patterns for handling errors in Go, based on production experience at Teleport. Covers the pitfall of shadowing original errors by wrapping them with fmt.Errorf (which breaks type assertions like os.IsNotExist), logging errors at the point of occurrence for traceability, and using runtime.Caller to get stack trace information. Introduces the open-source 'trace' package (gravitational/trace), which wraps errors while preserving the original error and adding file/line trace information, along with helper functions like trace.Wrap and trace.Errorf for cleaner debugging. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does wrapping an error with fmt.Errorf in Go break type checks like os.IsNotExist? Wrapping an error with fmt.Errorf creates a brand new error object, which shadows the original error value. Because the new error no longer carries the original type or value, calls like os.IsNotExist(err) will fail even though the underlying cause is still the same, since that check needs the original error type to work. _Developers debugging tricky Go error chains can find deeper explainers like this on daily.dev._ ### How can I get a stack trace when handling errors in Go, since Go doesn't have exceptions? Go lacks built-in exception stack traces, but runtime.Caller can report the file and line number of the function invocation on the calling goroutine's stack. This is the same mechanism used internally by Go's standard log library to report file and line info, and it can be leveraged in custom error-wrapping code to reconstruct a trace. _daily.dev surfaces practical Go debugging techniques for developers building production services._ ### What does the gravitational/trace Go package do differently from standard error wrapping? The trace package wraps an error while preserving the original error and accumulating file and line trace entries, accessible via an OrigError method, instead of shadowing it like fmt.Errorf does. It defines a TraceSetter interface so trace.Wrap can attach trace entries directly, and provides trace.Errorf as a drop-in replacement for fmt.Errorf that also records the call site. _daily.dev helps Go developers compare error-handling libraries before adopting one in production._ ## Similar posts on daily.dev - [How to Handle Errors in Go](https://daily.dev/posts/how-to-handle-errors-in-go-tlpqkl2og) · JetBrains · 25 upvotes · 1 comments - [Best Practices for Secure Error Handling in Go](https://daily.dev/posts/best-practices-for-secure-error-handling-in-go-4zsml2ahs) · JetBrains · 3 upvotes · 1 comments - [The Go Error Model Hidden in One Line](https://daily.dev/posts/the-go-error-model-hidden-in-one-line-oi5brk6yi) · Medium · 0 upvotes · 0 comments - [Unit Testing in Go - A Beginner's Guide](https://daily.dev/posts/unit-testing-in-go---a-beginner-s-guide-cqueimyzl) · freeCodeCamp · 19 upvotes · 0 comments - [Expanding errors with ReplaceAttr](https://daily.dev/posts/expanding-errors-with-replaceattr-vfxd8vujv) · Boldly Go · 10 upvotes · 1 comments --- Tags: [#golang](https://daily.dev/tags/golang) [View this post on daily.dev](https://daily.dev/posts/error-handling-in-go-programs-eq1vi28ks) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Error Handling in Go Programs","url":"https://daily.dev/posts/error-handling-in-go-programs-eq1vi28ks","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/error-handling-in-go-programs-eq1vi28ks"},"datePublished":"2026-08-23T12:19:46.482Z","dateModified":"2026-08-23T12:41:45.835Z","description":"Practical patterns for handling errors in Go, based on production experience at Teleport. Covers the pitfall of shadowing original errors by wrapping them with...","image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","thumbnailUrl":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/error-handling-in-go-programs-eq1vi28ks","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"golang","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Error Handling in Go Programs"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/error-handling-in-go-programs-eq1vi28ks#faq","mainEntity":[{"@type":"Question","name":"Why does wrapping an error with fmt.Errorf in Go break type checks like os.IsNotExist?","acceptedAnswer":{"@type":"Answer","text":"Wrapping an error with fmt.Errorf creates a brand new error object, which shadows the original error value. Because the new error no longer carries the original type or value, calls like os.IsNotExist(err) will fail even though the underlying cause is still the same, since that check needs the original error type to work. Developers debugging tricky Go error chains can find deeper explainers like this on daily.dev."}},{"@type":"Question","name":"How can I get a stack trace when handling errors in Go, since Go doesn't have exceptions?","acceptedAnswer":{"@type":"Answer","text":"Go lacks built-in exception stack traces, but runtime.Caller can report the file and line number of the function invocation on the calling goroutine's stack. This is the same mechanism used internally by Go's standard log library to report file and line info, and it can be leveraged in custom error-wrapping code to reconstruct a trace. daily.dev surfaces practical Go debugging techniques for developers building production services."}},{"@type":"Question","name":"What does the gravitational/trace Go package do differently from standard error wrapping?","acceptedAnswer":{"@type":"Answer","text":"The trace package wraps an error while preserving the original error and accumulating file and line trace entries, accessible via an OrigError method, instead of shadowing it like fmt.Errorf does. It defines a TraceSetter interface so trace.Wrap can attach trace entries directly, and provides trace.Errorf as a drop-in replacement for fmt.Errorf that also records the call site. daily.dev helps Go developers compare error-handling libraries before adopting one in production."}}]} ```