Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Minor formatting fixes #270

Merged
merged 1 commit into from
Mar 2, 2024
Merged

Minor formatting fixes #270

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions adr/ADR-41.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ This describes a feature of the NATS Server 2.11 that allows messages to be trac

## Prior Work

NATS supports tracking latency of Request-Reply service interactions, this is documented in ADR-3.
NATS supports tracking latency of Request-Reply service interactions, this is documented in [ADR-3](adr/ADR-3.md).

## Design

Expand All @@ -48,10 +48,11 @@ Not all messages are traced and there is no flag to enable it on all messages.

This mode of Activation allows headers to be added to any message that declares where to deliver the traces and inhibit delivery to the final application.

|Header|Description|
|`Nats-Trace-Dest`|A subject that will receive the Trace messages|
|`Nats-Trace-Only`|Prevents delivery to the final client, reports that it would have been delivered (`1`, `true`, `on`)|
|`Accept-Encoding`|Enables compression of trace payloads (`gzip`, `snappy`)|
| Header | Description |
|-------------------|------------------------------------------------------------------------------------------------------|
| `Nats-Trace-Dest` | A subject that will receive the Trace messages |
| `Nats-Trace-Only` | Prevents delivery to the final client, reports that it would have been delivered (`1`, `true`, `on`) |
| `Accept-Encoding` | Enables compression of trace payloads (`gzip`, `snappy`) |

The `Nats-Trace-Only` header can be used to prevent sending badly formed messages to subscribers, the servers will trace the message to its final destination and report the client it would be delivered to without actually delivering it. Additionally when this is set messages will also not traverse any Route, Gateway or Leafnode that does not support the Tracing feature.

Expand Down
Loading