Live data from Hacker News

Show HN: Checkmate, a server and infrastructure monitoring application

github.com

1–8 of 8 posts

Show HN: Checkmate, a server and infrastructure monitoring application

#1
We just released Checkmate 2.0 (formerly BlueWave Uptime). Originally designed as a simple uptime manager, Checkmate has evolved into an infrastructure monitoring tool.

With 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! )

Show HN: Checkmate, a server and infrastructure monitoring application
github.com

Re: Show HN: Checkmate, a server and infrastructure monitoring application

#5
post #2

Upvoted, looks neat. This is potentially a huge security issue though so I'd love to see more history/reviews before running this.

What makes this a security issue?

Running 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.

Re: Show HN: Checkmate, a server and infrastructure monitoring application

#7
post #5

Earlier quoted context omitted.

What makes this a security issue?

Running 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.

How would you solve the problem of collecting data from servers?

Re: Show HN: Checkmate, a server and infrastructure monitoring application

#8
post #5

Earlier quoted context omitted.

What makes this a security issue?

Running 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.

Zabbix, Nagios, and a whole suite of other very widely used IT monitoring tools do this. What makes this project more of a security issue?