1f349/dendrite
1
0
Fork 0
mirror of https://github.com/1f349/dendrite.git synced 2024-09-20 02:46:34 +01:00
Code Issues Packages Projects Releases Wiki Activity
7f114cc538
dendrite/docs/development/tracing/setup.md
Till 11d9b9db0e
Remove polylith/API mode (#2967) 
This removes most of the code used for polylith/API mode.

This removes the `/api` internal endpoints entirely. 

Binary size change roughly 5%: 
```
51437560 Feb 13 10:15 dendrite-monolith-server # old
48759008 Feb 13 10:15 dendrite-monolith-server # new
```
2023-02-14 12:47:47 +01:00

1.4 KiB
Raw Blame History

title parent grand_parent permalink
Setup OpenTracing Development /development/opentracing/setup

OpenTracing Setup

Dendrite uses Jaeger for tracing between microservices. Tracing shows the nesting of logical spans which provides visibility on how the microservices interact. This document explains how to set up Jaeger locally on a single machine.

Set up the Jaeger backend

The easiest way is to use the all-in-one Docker image:

$ docker run -d --name jaeger \
  -e COLLECTOR_ZIPKIN_HTTP_PORT=9411 \
  -p 5775:5775/udp \
  -p 6831:6831/udp \
  -p 6832:6832/udp \
  -p 5778:5778 \
  -p 16686:16686 \
  -p 14268:14268 \
  -p 14250:14250 \
  -p 9411:9411 \
  jaegertracing/all-in-one:1.18

Configuring Dendrite to talk to Jaeger

Modify your config to look like: (this will send every single span to Jaeger which will be slow on large instances, but for local testing it's fine)

tracing:
  enabled: true
  jaeger:
    serviceName: "dendrite"
    disabled: false
    rpc_metrics: true
    tags: []
    sampler:
      type: const
      param: 1

then run the monolith server:

./dendrite-monolith-server --tls-cert server.crt --tls-key server.key --config dendrite.yaml

Checking traces

Visit http://localhost:16686 to see traces under DendriteMonolith.