<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging and Troubleshooting on Dapr Docs</title><link>https://v1-18.docs.dapr.io/operations/troubleshooting/</link><description>Recent content in Debugging and Troubleshooting on Dapr Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://v1-18.docs.dapr.io/operations/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>Common issues when running Dapr</title><link>https://v1-18.docs.dapr.io/operations/troubleshooting/common_issues/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/operations/troubleshooting/common_issues/</guid><description>&lt;p>This guide covers common issues you may encounter while installing and running Dapr.&lt;/p>
&lt;h2 id="dapr-cant-connect-to-docker-when-installing-the-dapr-cli">Dapr can&amp;rsquo;t connect to Docker when installing the Dapr CLI&lt;/h2>
&lt;p>When installing and initializing the Dapr CLI, if you see the following error message after running &lt;code>dapr init&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>⌛ Making the jump to hyperspace...
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>❌ could not connect to docker. docker may not be installed or running
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Troubleshoot the error by ensuring:&lt;/p>
&lt;ol>
&lt;li>
&lt;p>&lt;a href="https://v1-18.docs.dapr.io/getting-started/install-dapr-selfhost/#step-4-verify-containers-are-running">The correct containers are running.&lt;/a>&lt;/p></description></item><item><title>Configure and view Dapr Logs</title><link>https://v1-18.docs.dapr.io/operations/troubleshooting/logs-troubleshooting/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/operations/troubleshooting/logs-troubleshooting/</guid><description>&lt;p>This section will assist you in understanding how logging works in Dapr, configuring and viewing logs.&lt;/p>
&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Logs have different, configurable verbosity levels.
The levels outlined below are the same for both system components and the Dapr sidecar process/container:&lt;/p>
&lt;ol>
&lt;li>error&lt;/li>
&lt;li>warn&lt;/li>
&lt;li>info&lt;/li>
&lt;li>debug&lt;/li>
&lt;/ol>
&lt;p>error produces the minimum amount of output, where debug produces the maximum amount. The default level is info, which provides a balanced amount of information for operating Dapr in normal conditions.&lt;/p></description></item><item><title>Dapr API Logs</title><link>https://v1-18.docs.dapr.io/operations/troubleshooting/api-logs-troubleshooting/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/operations/troubleshooting/api-logs-troubleshooting/</guid><description>&lt;p>API logging enables you to see the API calls your application makes to the Dapr sidecar. This is useful to monitor your application&amp;rsquo;s behavior or for other debugging purposes. You can also combine Dapr API logging with Dapr log events (see &lt;a href="https://v1-18.docs.dapr.io/operations/troubleshooting/logs-troubleshooting/">configure and view Dapr Logs&lt;/a> into the output if you want to use the logging capabilities together.&lt;/p>
&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>API logging is disabled by default.&lt;/p>
&lt;p>To enable API logging, you can use the &lt;code>--enable-api-logging&lt;/code> command-line option when starting the &lt;code>daprd&lt;/code> process. For example:&lt;/p></description></item><item><title>Profiling &amp; Debugging</title><link>https://v1-18.docs.dapr.io/operations/troubleshooting/profiling-debugging/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/operations/troubleshooting/profiling-debugging/</guid><description>&lt;p>In any real world scenario, an app might start exhibiting undesirable behavior in terms of resource spikes.
CPU/Memory spikes are not uncommon in most cases.&lt;/p>
&lt;p>Dapr allows users to start an on-demand profiling session using &lt;code>pprof&lt;/code> through its profiling server endpoint and start an instrumentation session to discover problems and issues such as concurrency, performance, cpu and memory usage.&lt;/p>
&lt;h2 id="enable-profiling">Enable profiling&lt;/h2>
&lt;p>Dapr allows you to enable profiling in both Kubernetes and stand-alone modes.&lt;/p></description></item></channel></rss>