mirror of
https://github.com/caddyserver/website.git
synced 2025-04-22 04:56:17 -04:00
caddyfile: tracing directive (#205)
* Add documentation for tracing directive * Update header in tracing.md Co-authored-by: Matt Holt <mholt@users.noreply.github.com> * Update documentation in tracing.md Co-authored-by: Matt Holt <mholt@users.noreply.github.com> * add link to the repository * add link to gRPC repo and w3c specification Co-authored-by: Andrii Kushch <> Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
This commit is contained in:
parent
7c2519209c
commit
c734cc3e64
2 changed files with 56 additions and 0 deletions
|
@ -62,6 +62,7 @@ Directive | Description
|
|||
**[route](/docs/caddyfile/directives/route)** | A group of directives treated literally as single unit
|
||||
**[templates](/docs/caddyfile/directives/templates)** | Execute templates on the response
|
||||
**[tls](/docs/caddyfile/directives/tls)** | Customize TLS settings
|
||||
**[tracing](/docs/caddyfile/directives/tracing)** | Integration with OpenTelemetry tracing
|
||||
**[try_files](/docs/caddyfile/directives/try_files)** | Rewrite that depends on file existence
|
||||
**[uri](/docs/caddyfile/directives/uri)** | Manipulate the URI
|
||||
|
||||
|
@ -104,6 +105,8 @@ Because matcher tokens all work the same, the various possibilities for the matc
|
|||
Many directives manipulate the HTTP handler chain. The order in which those directives are evaluated matters, so a default ordering is hard-coded into Caddy:
|
||||
|
||||
```caddy-d
|
||||
tracing
|
||||
|
||||
map
|
||||
root
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue