11516e0e4b
This renames zk-ca to opendev-ca and allows us to operate more than one ca on bridge. This way we can keep the CAs for ZooKeeper and Jaeger distinct (so that a compromise of the jaeger server could not be used to access the ZooKeeper cluster). This also starts a new jaeger-ca and uses it on the Jaeger server. Change-Id: I4e5bc4e3ccd78284ce785c971f7e6ad6e721f887
38 lines
1.0 KiB
ReStructuredText
38 lines
1.0 KiB
ReStructuredText
:title: Tracing
|
|
|
|
.. _tracing:
|
|
|
|
Tracing
|
|
#######
|
|
|
|
The Jaeger tracing server is installed on tracing.opendev.org. It is
|
|
intended to be used by Zuul, but may be used by other services in the
|
|
future. It displays information about Zuul operations in visual form.
|
|
|
|
At a Glance
|
|
===========
|
|
|
|
:Hosts:
|
|
* https://tracing.opendev.org
|
|
:Ansible:
|
|
* https://opendev.org/opendev/system-config
|
|
* :git_file:`playbooks/roles/jaeger`
|
|
* :git_file:`playbooks/service-tracing.yaml`
|
|
:Projects:
|
|
* https://www.jaegertracing.io/
|
|
* https://www.jaegertracing.io/docs/latest/getting-started/
|
|
:Bugs:
|
|
* https://storyboard.openstack.org/#!/project/748
|
|
|
|
Overview
|
|
========
|
|
|
|
Apache is configured as a reverse proxy and there is an internal
|
|
Badger database stored at ``/var/jaeger/badger``.
|
|
|
|
Zuul sends telemetry information to Jaeger via the gRPC protocol.
|
|
|
|
An internal CA is used to provide and validate client certificates for
|
|
the gRPC connection to Jaeger. The CA is distinct from other internal
|
|
CAs (for example, ZooKeeper) for security purposes.
|