Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Top 23 Troubleshooting Open-Source Projects
-
mitmproxy
An interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Wireshark
Read-only mirror of Wireshark's Git repository at https://gitlab.com/wireshark/wireshark. ⚠️ GitHub won't let us disable pull requests. ⚠️ THEY WILL BE IGNORED HERE ⚠️ Upload them at GitLab instead.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
kubectl-debug
This repository is no longer maintained, please checkout https://github.com/JamesTGrant/kubectl-debug.
-
sysdig-inspect
Sysdig Inspect - A powerful opensource interface for container troubleshooting and security investigation
-
fyi
Little bits of information that you may find useful when interacting with Expo tools and service. Append the markdown filename to https://expo.fyi/ to get a quick link to it.
-
k8s-pod-restart-info-collector
Automated troubleshooting of Kubernetes Pods issues. Collect K8s pod restart reasons, logs, and events automatically.
-
crash-diagnostics
Crash-Diagnostics (Crashd) is a tool to help investigate, analyze, and troubleshoot unresponsive or crashed Kubernetes clusters.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: Apple's M4 Has Reportedly Adopted the ARMv9 Architecture | news.ycombinator.com | 2024-05-24Mainly this was just myself getting irritated at MS Teams and trying to figure out what it was doing. It was a couple years ago and my current company doesn't use teams, thankfully, so I can't really see if its still valid.
From what I remember..
There are files on the disk that get updated/overwritten with pulls from the server every time it launches. Somewhere in AppData I think. A few of these are config files (with lots of interesting looking settings, including beta features).
One of the config entries specifies a telemetry endpoint (which, you _could_ figure out with a network tracing tool but there are a ton of MS telemetry endpoints your machine is probably talking to. Best to just grab the one explicitly being used from the config like this). I forget the full name of the setting but the name pretty clearly indicates its for telemetry, and the file is clearly a config file. If you can't find it just by browsing the structure, try a multi-file search tool and look for 'telemetry' or URL/hostnames.
You can't really change the value on disk and make it just take effect from there, since it gets downloaded from the server and overwritten before Teams loads. There might be some tricks you can do locally to persist the change but nothing seemed to work for me. You could override response from server via mitmproxy but that requires finding where it comes across the wire at launch time and then building a script/config to replace it.
Anyway, you can block that telemetry endpoint from a firewall and see your memory bloat. Or you can intercept that endpoint in any mitm proxy. I went with this [mitmproxy](https://mitmproxy.org/). From there you can capture the content it sends to the endpoint, or even change the response the server sends (Teams just seems to expect a 200 code back).
The telemetry data itself is some kind of streaming event format. I think I even found documentation on the structure on some microsoft website, so its likely a reused format.
It's pretty straightforward.
I couldn't spend too much time on it and now it's not something I even use, but some cool things you might want to try if you dive deeper into this:
- Overwrite the config file as it returns from the server, to turn on EU data protection, change various functionality you're not supposed to, or flip some feature flags.
- Figure out if there's a feature flag or even other overwrite to fully disable the metrics so they aren't even collected, from anywhere in the app.
- Intercept telemetry, return an 'OK' response and drop the data from telemetry, or maybe document what they collect more definitively if you think there's interest somewhere. This keeps your privacy but doesn't really do anything for performance.
- Interfere with the data before actually returning it, maybe try playing with event contents and channel/user indicators. Microsoft probably won't like this if they notice, but it's unlikely they'll even notice.
Project mention: Cisco to Acquire Cloud Native Networking and Security Leader Isovalent | news.ycombinator.com | 2023-12-21They would have had to add a few externals to get to Graduated but it's definitely a minority:
https://github.com/cilium/cilium/blob/main/MAINTAINERS.md
For execsnoop, people running systems with DTrace can find the same:
* https://github.com/jorgev/dtrace-scripts/blob/master/execsno...
On macOS Monterey+ you'll probably have to install the Kernel Debug Kit per:
* https://developer.apple.com/forums/thread/692444
The Linux variant was written Brendan Gregg (who previous did a lot of work on Solaris, where DTrace was created):
* https://github.com/brendangregg/perf-tools/blob/master/execs...
To begin with Wireshark, visit their official website for the download. The installation process is straightforward, but attention should be paid to the installation of command-line tools, which may require separate steps. Upon launching Wireshark, users are greeted with a selection of network interfaces as seen below. Choosing the correct interface, such as the loopback for local server debugging, is crucial for capturing relevant data.
curl is fantastic. There's also HTTPStat which provides a waterfall visualization on top of curl timings: https://github.com/reorx/httpstat
There's also Skytrace (made by yours truly), which provides timing info as a waterfall visualization inspired by HTTPStat + lots more (syntax highlighting for responses, built-in JMESPath support, command-line assertions and checks etc) - https://github.com/artilleryio/artillery/tree/main/packages/...
As a reminder, Trippy combines the functionality of traceroute and ping and is designed to assist with the analysis of networking issues. You can think of it as a modern, cross platform, Rust based version of tools such as mtr, with a bunch of advanced features and a fancy TUI.
Unlike the other tools mentioned in this post, Kubevious has no way of changing the cluster state. It is intended solely as an observability tool, focusing on potential issues in your cluster. It highlights potential threats and risks for every resource you may run.
https://github.com/bloomberg/pystack/blob/a971a4ced371a5859f...
So i found out this client was using unimodules for a lot of his libraries. But unimodules has been deprecated and merged into expo now. So now I followed the instructions here, and it looks like I just have migrated my application into expo only as it(expo-upgrade) created created a .expo folder now and also bumped package.json libraries to latest versions.
Project mention: Introducing Komoplane: viewer for Crossplane resources | /r/kubernetes | 2023-07-03To try out Komoplane, head over to: https://github.com/komodorio/komoplane. You can install it via a Helm chart, or you can just run it as standalone binary on your laptop. Don't forget to give it a star if you liked it ;)
Troubleshooting related posts
-
Apple's M4 Has Reportedly Adopted the ARMv9 Architecture
-
Wireshark & tcpdump: A Debugging Power Couple
-
Ask HN: Fiddler Alternatives
-
Best Hacking Tools for Beginners 2024
-
Why is my LG Washing Machine using 3.6GB of data/day?
-
The Gems of Moreutils
-
AirBnb Wifi Safety Precaution needed?
-
A note from our sponsor - InfluxDB
www.influxdata.com | 3 Jun 2024
Index
What are some of the best open-source Troubleshooting projects? This list will help you:
Project | Stars | |
---|---|---|
1 | mitmproxy | 34,737 |
2 | cilium | 18,937 |
3 | perf-tools | 9,668 |
4 | netshoot | 7,843 |
5 | Sysdig | 7,620 |
6 | Wireshark | 6,773 |
7 | httpstat | 5,597 |
8 | tcpdump | 2,574 |
9 | mtr | 2,553 |
10 | kubectl-debug | 2,292 |
11 | kubevious | 1,552 |
12 | Homer | 1,539 |
13 | pystack | 960 |
14 | sysdig-inspect | 941 |
15 | fyi | 684 |
16 | ios-crash-dump-analysis-book | 583 |
17 | troubleshoot | 533 |
18 | Reset-Windows-Update-Tool | 474 |
19 | apache2buddy | 379 |
20 | k8s-pod-restart-info-collector | 313 |
21 | grml | 273 |
22 | komoplane | 214 |
23 | crash-diagnostics | 180 |
Sponsored