Logging on Dapr Docs

Logs

Mon, 01 Jan 0001 00:00:00 +0000

Dapr produces structured logs to stdout, either in plain-text or JSON-formatted. By default, all Dapr processes (runtime, or sidecar, and all control plane services) write logs to the console (stdout) in plain-text. To enable JSON-formatted logging, you need to add the --log-as-json command flag when running Dapr processes.

Note

If you want to use a search engine such as Elastic Search or Azure Monitor to search the logs, it is strongly recommended to use JSON-formatted logs which the log collector and search engine can parse using the built-in JSON parser.

Log schema

Dapr produces logs based on the following schema:

How-To: Set up Fluentd, Elastic search and Kibana in Kubernetes

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

Kubernetes (> 1.14)
kubectl
Helm 3

Install Elastic search and Kibana

Create a Kubernetes namespace for monitoring tools
```
kubectl create namespace dapr-monitoring
```

Add the helm repo for Elastic Search

helm repo add elastic https://helm.elastic.co
helm repo update

Install Elastic Search using Helm

By default, the chart creates 3 replicas which must be on different nodes. If your cluster has fewer than 3 nodes, specify a smaller number of replicas. For example, this sets the number of replicas to 1:

How-To: Set-up New Relic for Dapr logging

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

Perpetually free New Relic account, 100 GB/month of free data ingest, 1 free full access user, unlimited free basic users

Background

New Relic offers a Fluent Bit output plugin to easily forward your logs to New Relic Logs. This plugin is also provided in a standalone Docker image that can be installed in a Kubernetes cluster in the form of a DaemonSet, which we refer as the Kubernetes plugin.

This document explains how to install it in your cluster, either using a Helm chart (recommended), or manually by applying Kubernetes manifests.