Show HN: Checkmate, a server and infrastructure monitoring application
21 points by gorkemcetin 7 months ago | 7 commentsWith the addition of our lightweight Go-based server agent (Capture) it's possible to monitor key metrics like CPU, RAM, and disk usage across remote servers.
We’re now exploring new features, including enhanced notifications, advanced configuration options, DNS monitoring, and status pages (which are almost ready to launch btw). There are no plans for synthetic monitoring, APM, log management, traces etc. It'll hopefully stay as small as possible.
It's still the early days for Checkmate. The project gained some traction with 31 contributors and this version itself had 13 contributors.
- Server: https://github.com/bluewave-labs/checkmate
- Agent: https://github.com/bluewave-labs/capture
- Demo: https://checkmate-demo.bluewavelabs.ca/ (The username is uptimedemo@demo.com and the password is Demouser1! )
- cweagans 7 months agoAt risk of sounding like the dropbox/rsync guy, is this materially different from what you can accomplish with Prometheus, the Blackbox exporter, (optionally) the node exporter, and Grafana?
- johng 7 months agoUpvoted, looks neat. This is potentially a huge security issue though so I'd love to see more history/reviews before running this.
- gorkemcetin 7 months agoWould love to learn more about this. Could you please share some more information?
- KetoManx64 7 months agoWhat makes this a security issue?
- johng 7 months agoRunning an agent on every server that reports back to the master server is a huge security vector.
Running a daemon on a server that scrapes data is also a security vector.
- KetoManx64 7 months agoZabbix, Nagios, and a whole suite of other very widely used IT monitoring tools do this. What makes this project more of a security issue?
- gorkemcetin 7 months agoHow would you solve the problem of collecting data from servers?
- KetoManx64 7 months ago
- johng 7 months ago
- gorkemcetin 7 months ago