Configure and view Dapr Logs

    This section will assist you in understanding how logging works in Dapr, configuring and viewing logs.

    Logs have different, configurable verbosity levels. The levels outlined below are the same for both system components and the Dapr sidecar process/container:

    1. error
    2. warning
    3. info
    4. debug

    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.

    To set the output level, you can use the command-line option. For example:

    This will start the Dapr runtime binary with a log level of error and the Dapr Actor Placement Service with a log level of debug.

    To set the log level when running your app with the Dapr CLI, pass the log-level param:

    1. dapr run --log-level warning node myapp.js
    1. ./placement --log-level warning

    When running Dapr with the Dapr CLI, both your app’s log output and the runtime’s output will be redirected to the same session, for easy debugging. For example, this is the output when running Dapr:

    1. dapr run node myapp.js
    2. ✅  You are up and running! Both Dapr and your app logs will appear here.
    4. == APP == App listening on port 3000!
    5. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="starting Dapr Runtime -- version 0.3.0-alpha -- commit b6f2810-dirty"
    6. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="log level set to: info"
    7. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="standalone mode configured"
    9. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="loaded component statestore (state.redis)"
    10. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="loaded component messagebus (pubsub.redis)"
    11. == DAPR == 2019/09/05 12:26:43 redis: connecting to localhost:6379
    12. == DAPR == 2019/09/05 12:26:43 redis: connected to localhost:6379 (localAddr: [::1]:56734, remAddr: [::1]:6379)
    13. == DAPR == time="2019-09-05T12:26:43-07:00" level=warning msg="failed to init input bindings: app channel not initialized"
    14. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="actor runtime started. actor idle timeout: 1h0m0s. actor scan interval: 30s"
    15. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="actors: starting connection attempt to placement service at localhost:50005"
    16. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="http server is running on port 56730"
    17. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="gRPC server is running on port 56731"
    18. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="dapr initialized. Status: Running. Init Elapsed 8.772922000000001ms"
    19. == DAPR == time="2019-09-05T12:26:43-07:00" level=info msg="actors: established connection to placement service at localhost:50005"

    You can set the log level individually for every sidecar by providing the following annotation in your pod spec template:

    When deploying Dapr to your cluster using Helm 3.x, you can individually set the log level for every Dapr system component:

    1. helm install dapr dapr/dapr --namespace dapr-system --set <COMPONENT>.logLevel=<LEVEL>

    Components:

    • dapr_operator
    • dapr_sidecar_injector

    Example:

    1. helm install dapr dapr/dapr --namespace dapr-system --set dapr_operator.logLevel=error

    Dapr logs are written to stdout and stderr. This section will guide you on how to view logs for Dapr system components as well as the Dapr sidecar.

    Sidecar Logs

    1. NAME                                        READY     STATUS    RESTARTS   AGE
    2. addapp-74b57fb78c-67zm6                     2/2       Running   0          40h

    Next, get the logs for the Dapr sidecar container:

    System Logs

    Dapr runs the following system pods:

    • Dapr operator
    • Dapr sidecar injector
    • Dapr placement service

    Operator Logs

    1. kubectl logs -l app=dapr-operator -n dapr-system
    2. time="2019-09-05T19:03:43Z" level=info msg="log level set to: info"
    3. time="2019-09-05T19:03:43Z" level=info msg="starting Dapr Operator -- version 0.3.0-alpha -- commit b6f2810-dirty"
    4. time="2019-09-05T19:03:43Z" level=info msg="Dapr Operator is started"

    Note: If Dapr is installed to a different namespace than dapr-system, simply replace the namespace to the desired one in the command above

    Sidecar Injector Logs

    1. kubectl logs -l app=dapr-sidecar-injector -n dapr-system
    2. time="2019-09-03T21:01:12Z" level=info msg="log level set to: info"
    3. time="2019-09-03T21:01:12Z" level=info msg="starting Dapr Sidecar Injector -- version 0.3.0-alpha -- commit b6f2810-dirty"
    4. time="2019-09-03T21:01:12Z" level=info msg="Sidecar injector is listening on :4000, patching Dapr-enabled pods"

    Note: If Dapr is installed to a different namespace than dapr-system, simply replace the namespace to the desired one in the command above

    Viewing Placement Service Logs

    1. kubectl logs -l app=dapr-placement -n dapr-system
    2. time="2019-09-03T21:01:12Z" level=info msg="log level set to: info"
    3. time="2019-09-03T21:01:12Z" level=info msg="starting Dapr Placement Service -- version 0.3.0-alpha -- commit b6f2810-dirty"
    4. time="2019-09-03T21:01:12Z" level=info msg="placement Service started on port 50005"

    Note: If Dapr is installed to a different namespace than dapr-system, simply replace the namespace to the desired one in the command above

    The examples above are specific specific to Kubernetes, but the principal is the same for any kind of container based environment: simply grab the container ID of the Dapr sidecar and/or system component (if applicable) and view its logs.