<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Trace on random thoughts</title><link>https://riad.run/tags/trace/</link><description>Recent content in Trace on random thoughts</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 20 Aug 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://riad.run/tags/trace/feed.xml" rel="self" type="application/rss+xml"/><item><title>Trace Logging in Golang</title><link>https://riad.run/posts/trace-in-golang/</link><pubDate>Sun, 20 Aug 2023 00:00:00 +0000</pubDate><guid>https://riad.run/posts/trace-in-golang/</guid><description>&lt;p&gt;&lt;em&gt;Disclaimer: This article is not about &lt;code&gt;runtime/trace&lt;/code&gt; package or trace profiling functionalities.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Tracing is used to observe code execution paths. If you log something in a function and you see that output in the log file, then you know that the function has been executed. There is a log level defined in different logger implementations called &lt;code&gt;TRACE&lt;/code&gt;, which is the lowest log level in most loggers. The log won&amp;rsquo;t be present in the production environment, but when debugging, you&amp;rsquo;ll receive the traces. This is useful in situations where a debugger is not accessible.&lt;/p&gt;</description></item></channel></rss>