— because when you’re chasing microseconds, your tools can’t afford to blur them. Have you used timestamping tools in high‑throughput pipelines? Share your setup below or tag us with #tsprint.
[14:23:05.123456] "type":"ping" [14:23:05.123478] "type":"pong" Notice the 22‑microsecond delta — perfect for race condition analysis. for i in 1..100; do echo "data $i"; sleep 0.01; done | \ tsprint --timestamp --relative | \ grep "data 50" 3. High‑volume log tailing with rate limiting tail -f /var/log/nginx/access.log | tsprint --rate 10 --format json Only 10 lines per second reach your terminal, but every timestamp remains accurate. How tsprint differs from ts (moreutils) | Feature | ts (moreutils) | tsprint | |-----------------------|------------------------|----------------------------| | Timestamp precision | Second | Nanosecond | | Output formats | Plain text | JSON, CSV, custom template | | Non‑blocking I/O | No | Yes | | Rate limiting | No | Yes | | Real‑time streaming focus | Partial | Designed for it | Getting started Install tsprint (assuming it’s packaged or available via cargo/go):
command_that_streams | tsprint Advanced:
Basic usage:
# Example for a Rust build cargo install tsprint brew install tsprint
tsprint --help Let’s simulate a sensor emitting temperature readings every 50ms, and use tsprint to see exactly when each reading arrives:
Oeps! Het ziet er naar uit dat je een verouderde browser gebruikt. Dit kan er voor zorgen dat deze website niet helemaal correct functioneert. We raden je ten sterkste aan om de laatste versie van je favoriete browser af te halen. Met een recente browser kan je op veilige en optimale wijze rondsurfen.