Better opentracing config comment

pull/5544/head
Jorik Schellekens 2019-06-25 18:24:38 +01:00
parent dde461814d
commit 34235a45e4
2 changed files with 20 additions and 12 deletions

View File

@ -1354,16 +1354,18 @@ password_config:
# example_option: 'things'
## Tracer ##
## Opentracing ##
# These settings enable opentracing which implements distributed tracing
# This allows you to observe the causal chain of events across servers
# including requests, key lookups etc. across any server running
# synapse or any other other services which supports opentracing.
# (specifically those implemented with jaeger)
#tracer:
#opentracing:
# # Enable / disable tracer
# tracer_enabled: false
# # The list of users who's requests will be traced
# # The list is a list of regex which is matched against the user_id
# user_whitelist:
# - "*"
# # The list of homeservers we wish to trace across
# # The list is a list of regex which is matched against the homeserver name
# # The list of homeservers we wish to expose our current traces to.
# # The list is a list of regexes which are matched against the
# # servername of the homeserver
# homeserver_whitelist:
# - "*"
# - ".*"

View File

@ -44,14 +44,20 @@ class TracerConfig(Config):
def generate_config_section(cls, **kwargs):
return """\
## Opentracing ##
# These settings enable opentracing which implements distributed tracing
# This allows you to observe the causal chain of events across servers
# including requests, key lookups etc. across any server running
# synapse or any other other services which supports opentracing.
# (specifically those implemented with jaeger)
#opentracing:
# # Enable / disable tracer
# tracer_enabled: false
# # The list of homeservers we wish to trace across
# # The list is a list of regex which is matched against the homeserver name
# # The list of homeservers we wish to expose our current traces to.
# # The list is a list of regexes which are matched against the
# # servername of the homeserver
# homeserver_whitelist:
# - "*"
# - ".*"
"""