| trippy | rhit | |
|---|---|---|
| 18 | 8 | |
| 3,019 | 810 | |
| - | - | |
| 9.8 | 7.3 | |
| 7 days ago | 6 months ago | |
| Rust | Rust | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
trippy
-
Apnic: Cgnat is harming internet innovation (2022)
[3] https://github.com/fujiapple852/trippy/issues/1104
- FLaNK Stack Weekly 11 Dec 2023
-
Trippy – A Network Diagnostic Tool
You are right that showing packet loss for intermediate hops is a frequent source of confusion.
Rather than leave it out, I added a status column which shows different statuses for intermediate hops (blue if the hop responds to less than 100% of probes and brown if it responds to 0%) vs the target hop (amber and red).
Where this breaks down is when dealing with ECMP for UDP & TCP tracing, as a given hop (ttl) may represent the target for a given round of tracing but not for the next. The mistake, imho, is to associate _any_ data with a hop (ttl) rather than the hop in the context of a tracing flow.
That is why Trippy had a number of features aimed at helping with ECMP, such as Paris and Dublin tracing, and the ability to filter tracing by unique flow id. I've covered these quite a bit in the 0.8.0 [0] and 0.9.0 [1] release notes if you want to know more.
[0] https://github.com/fujiapple852/trippy/releases/tag/0.8.0
- Trippy: A Network Diagnostic Tool
- Trippy: Network Diagnostic Tool
-
Trippy 0.9.0 Release
Tracing flows: breakdown complex UDP/TCP ECMP traces into individual flows (i.e. common network path); render a chart of flows in GraphViz DOT format (example)
-
[Media] Introducing Trippy: A Network Diagnostic Tool
u/queiss_ the 0.8.0 release note has a section covering this, but the TL;DR is:
rhit
-
Your favourite Rust CLI utilities this year?
As two of the tools I made I already listed here, may I suggest also lfs (which tells you about your disks and available space) and rhit (if you have a nginx server running) ?
- Semantic HTML conveys meaning
- Rhit – Nginx log explorer that leaves nothing behind, no temp file, no database
- Rhit – a Nginx log explorer, it leaves nothing behind, no temp file, no database
- Rhit - NGINX log navigator that reads even gzipped logs, does some analysis and tells you about it in pretty tables without storing or polluting anything
- Show HN: Rhit, a Nginx Log Explorer
- Rhit, a command-line nginx log explorer I just made
- Rhit, a small tool I just made to analyze your existing nginx logs
What are some alternatives?
mtr - Official repository for mtr, a network diagnostic tool
taplo - A TOML toolkit written in Rust
mezura - A fairly fast, fairly accurate and very customizable stats generator and growth tracker, for programming projects, in the form of a CLI executable, written in Rust.
dusage - 💾 A command line disk usage information tool.
pingapi - Ping API for piracy.moe
log4rs - A highly configurable logging framework for Rust
bongo - A cross-platform MongoDB dashboard CLI Viewer
hprof-slurp - JVM heap dump analyzer
weaver - API tool,but egui style and rusty
nginx-rs - Nginx module written in Rust
pyroscope-rs - Pyroscope Profiler for Rust. Profile your Rust applications.
ubi - The Universal Binary Installer