I made a thingy.
Or rather, I vibe coded a thingy. Essentially, I got bored during a meeting and rather than chew on my pen, I spent half an hour putting together a very simple monitoring server for our estate in order to power our status page, as well as to hopefully syndicate to the wider EOSC Node infrastructure.
I was aware that tools like this exist, but those all seemed needlessly complex for what I was after, and so I bashed together a quick node server. Tools like ARGO are fine, and are very capable, but aren’t containerised currently and require heavy weight things like backend databases and stuff. Not war I was after.
Anyway, this server is fed a config.json that lists all the server groups in your estate, endpoints and poll periods, and then exposes their status via API. This is then picked up by a javascript front end running in an S3 bucket.
What’s notable is that I didn’t actually write a single line of code here, from scratch to deployment I described what I wanted to the AI as if I was talking to one of my junior developers, and verified its working as I would a series of pull requests.
I’ve got a blog post coming about how I feel about this, and what I think it means career wise, but for now, enjoy this new (hopefully useful) tool.