node_exporter VS chisel

$ wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz $ tar -xzvf node_exporter-1.7.0.linux-amd64.tar.gz

Node Exporter

The Prometheus node_exporter can provide this information, doesn't require root. You could run it as a systemd user unit if you don't have root.

I personally find it best to learn through experimentation. Start with reading a bit about Prometheus and Grafana through their docs, and then familiarise yourself with setting up a local Prometheus + Grafana instance either locally or with docker using docker-compose, along with something to generate /metrics endpoint for Prometheus to scrape from such as a custom Prometheus exporter in Python or using Node Exporter.

Your best bet might be to fork node_exporter to get you more verbose socket stats: https://github.com/prometheus/node_exporter/blob/master/collector/sockstat_linux.go

I use Grafana + Prometheus + Node Exporter.

Crazy idea, can't NX devices run Docker? I wonder if the node_exporter would work.

Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and application/database latency. CPU and memory utilization isn't a great metric to alert on a lot of the time.

You may setup node exporter and collect metrics with prometheus for example. Its not quite "simple" way, but still you may find it useful.

chisel - SSH under the hood, but still uses a custom client binary. Supports auto certs from LetsEncrypt. Written in Go.

Looking at the perf https://github.com/jpillora/chisel/blob/master/test/bench/pe... it looks not too bad!

I have a few TCP based utilities. I was thinking I need to make websocket equivalents for it to work on the web, but happy to see this project, I will be evaluating this soon, it should save me some time.

Thanks for sharing!

Personally I use https://github.com/jpillora/chisel as a reverse Proxy through nginx, then connect through it using OpenVPN to bypass a similarly restrictive firewall. But this discussion is filled with other, similar hacks, I may have to try some of them.

To keep everything secure, each chisel client has a separate TLS private key. That lets my reverse proxy authenticate the client before allowing a connection to the Chisel backend service. And on the Chisel backend service side, the --auth= part allows that particular client to bind to the specific XXX port within that Docker container. https://github.com/jpillora/chisel/blob/master/example/users.json

I love it in the context of hacking actually. When working on HackTheBox machines or other CTFs you sometimes need to deploy tools onto the machine like these:

* https://github.com/jpillora/chisel

rclone and chisel. rclone is a high quality swiss-army knife for selfhosting. It does a lot of things and it does all of those things surprisingly well. chisel provides an TCP/UDP tunnel over websockets. When heroku used to be free, I had a couple of chisel instances running on Heroku, which I would use, occasionally, to quickly access any of my locally hosted apps or servers.

GitHub - jpillora/chisel: A fast TCP/UDP tunnel over HTTP

You should try Chisel https://github.com/jpillora/chisel