mirror of
https://github.com/ceph/ceph
synced 2025-01-25 04:24:24 +00:00
46 lines
955 B
ReStructuredText
46 lines
955 B
ReStructuredText
================
|
|
Tracing Services
|
|
================
|
|
|
|
.. _cephadm-tracing:
|
|
|
|
|
|
Jaeger Tracing
|
|
==============
|
|
|
|
Ceph uses Jaeger as the tracing backend. in order to use tracing, we need to deploy those services.
|
|
|
|
Further details on tracing in ceph:
|
|
|
|
`Ceph Tracing documentation <https://docs.ceph.com/en/latest/jaegertracing/#jaeger-distributed-tracing/>`_
|
|
|
|
Deployment
|
|
==========
|
|
|
|
Jaeger services consist of 3 services:
|
|
|
|
1. Jaeger Agent
|
|
|
|
2. Jaeger Collector
|
|
|
|
3. Jaeger Query
|
|
|
|
Jaeger requires a database for the traces. we use ElasticSearch (version 6) by default.
|
|
|
|
|
|
To deploy jaeger tracing service, without ElasticSearch:
|
|
|
|
#. Deploy jaeger services, with a new elasticsearch container:
|
|
|
|
.. prompt:: bash #
|
|
|
|
ceph orch apply jaeger
|
|
|
|
|
|
#. Deploy jaeger services, with existing elasticsearch cluster and existing jaeger query (deploy agents and collectors):
|
|
|
|
.. prompt:: bash #
|
|
|
|
ceph orch apply jaeger --without-query -es_nodes=ip:port,..
|
|
|