Skip to content

Conversation

@jstirnaman
Copy link
Contributor

@jstirnaman jstirnaman commented Oct 21, 2025

… examples

  • Add precision comparison table across v1, v2, v3 write APIs
  • Add tabbed code examples for different precision values
  • Update OpenAPI specs with short-form precision values (ns, us, ms, s)

TODO

> [!Note]
> A bug currently prevents abbreviated precision values (`ns`, `n`, `us`, `u`, `ms`, `s`) from working with the `/api/v3/write_lp` endpoint. Use the full names (`nanosecond`, `microsecond`, `millisecond`, `second`) instead. Abbreviated values will be supported in a future release.

Closes #6472, #6475

… examples

- Add precision comparison table across v1, v2, v3 write APIs
- Document auto precision detection with exponential notation (5e9, 5e12, 5e15)
- Add tabbed code examples for different precision values
- Update write endpoint recommendations for new workloads
- Add Telegraf output plugin guidance (v1.x and v2.x)
- Update OpenAPI specs with short-form precision values (ns, us, ms, s)
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.

Update /api/v3/write_lp precision parameter docs for additional short forms Inconsistent precision syntax in /api/v3/write_lp docs

1 participant