From a1cf8023c6bfda3f4d6ddf6146661ed883b133b0 Mon Sep 17 00:00:00 2001 From: Jarrod Johnson Date: Fri, 8 Aug 2025 14:30:30 -0400 Subject: [PATCH] Clarify that nodesensors csv may have a different order CSV must keep sensors grouped and consistent, so it waits until it gathers all results to sort. Normally, it presents the results as quickly as the API provides it. This results in some different ordering for the "fast as API provides it" versus "delayed to group the values together" behavior. --- confluent_client/doc/man/nodesensors.ronn | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/confluent_client/doc/man/nodesensors.ronn b/confluent_client/doc/man/nodesensors.ronn index 483bffc3..f7dfe360 100644 --- a/confluent_client/doc/man/nodesensors.ronn +++ b/confluent_client/doc/man/nodesensors.ronn @@ -19,7 +19,9 @@ interval of 1 second is used. ## OPTIONS * `-c`, `--csv`: - Organize output into CSV format, one sensor per column. + Organize output into CSV format, one sensor per column. Note that while normally nodesensors reports + sensors in order as returned by server, CSV output enforces consistency by sorting after receiving + the results, which may have a different ordering than non-CSV usage of nodesensors. * `-i`, `--interval`=**SECONDS**: Repeat data gathering waiting, waiting the specified time between samples. Unless `-n` is