Skip to content

Clarify NATS stability and log shipper relationship#2359

Merged
kcmartin merged 1 commit intomainfrom
fix/nats-log-shipper-consistency
Feb 25, 2026
Merged

Clarify NATS stability and log shipper relationship#2359
kcmartin merged 1 commit intomainfrom
fix/nats-log-shipper-consistency

Conversation

@kcmartin
Copy link
Contributor

Summary

  • Replace "dusty corner" / "unofficial, experimental" language with a clearer description of NATS as an internal transport without a versioned API or stability guarantee
  • Acknowledge that the log shipper uses NATS internally and, as a Fly-maintained project, is more likely to stay compatible with infrastructure changes than a custom NATS client

Closes #2319

Replace "dusty corner" language with a clearer description of NATS as
an internal transport without a stability guarantee. Acknowledge that
the log shipper uses NATS internally and is more likely to stay
compatible with changes as a maintained Fly project.

Closes #2319
@kcmartin kcmartin merged commit 59e591f into main Feb 25, 2026
1 of 2 checks passed
@kcmartin kcmartin deleted the fix/nats-log-shipper-consistency branch February 25, 2026 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue with the "Logs API options for programmatic access" doc

1 participant