| commit | 344af7af7e26c09335497a426132aec05473a347 | [log] [tgz] |
|---|---|---|
| author | czichy <thoralf.czichy@nokia.com> | Tue Nov 26 11:08:33 2019 +0200 |
| committer | czichy <thoralf.czichy@nokia.com> | Tue Nov 26 11:09:18 2019 +0200 |
| tree | 3454a5f36748ece3906e50d9244dd5b2f75d3394 | |
| parent | 53f535ce1404afdb450ddb7019e0a8d0b5c1b89f [diff] |
Adding extra line that src files are part of RIC platform project Change-Id: Ieb9fa5de205c2323edf4473e717ffa354c7ecaae Signed-off-by: czichy <thoralf.czichy@nokia.com>
This repository contains jaeger configuration files, like the helm charts
Currently only supported configuration is jaeger-all-in-one deployment. The helm chart defines following three services.
Jaeger agent receives trace data from jaeger client(s) with UDP to ports 5775 or 6831 or 6832. So the jaeger pods needs to expose these ports and the jaeger agent service IP address should be available with DNS.
With these helm charts the DNS entry will be jaeger-all-in-one-agent.
Jaeger collector receives trace data from jaeger agent(s) with TCP to ports 14267 or 14268 or 9411. Jaeger pod need to expose these ports and the collector service IP address should be available with DNS
With these helm charts the DNS entry will be jaeger-all-in-one-collector.
Jaeger query implements a web service for quering trace data. It should expose a http port, for example 80.
With these helm charts the DNS entry will be jaeger-all-in-one-query.
A config map for creating trace client configuration is provided. Currently it configures a disabled tracer client.