![]() By default you might want opentracing off, but on for a particular ingress. Similarly, you might want opentracing globally on, but disabled for a specific endpoint. To achieve this, `opentracing_propagate_context` cannot be set when combined with `opentracing off` A new annotation, `enable-opentracing` allows more fine grained control of opentracing for specific ingresses. |
||
---|---|---|
.. | ||
nginx-configuration | ||
third-party-addons | ||
basic-usage.md | ||
cli-arguments.md | ||
convert_arguments_to_doc.py | ||
custom-errors.md | ||
default-backend.md | ||
exposing-tcp-udp-services.md | ||
external-articles.md | ||
fcgi-services.md | ||
ingress-path-matching.md | ||
miscellaneous.md | ||
monitoring.md | ||
multiple-ingress.md | ||
tls.md |