News for hackers. Stuff that matters.
Re:Monitoring tiny web services by tedmiston on Saturday July 09, 2022 @10:35PM (#32041336)
New Relic also offers a similar uptime monitoring with a generous free tier via their Synthetics service.

https://newrelic.com/platform/synthetics

Re:Monitoring tiny web services by packetslave on Saturday July 09, 2022 @11:33PM (#32041600)
I wish New Relic would support plain old ICMP ping. That would be nice. You used to be able to implement it using their Scripted API thing (which is just sandboxed Node), but at some point they broke raw socket support, which broke every ping NPM in existence. I think you can still make it work if you run a private minion, but that's more effort than I want to spend.
Re:Monitoring tiny web services by teh_klev on Sunday July 10, 2022 @12:13AM (#32041788)
> but at some point they broke raw socket support

Sockets are a transport layer feature e.g. TCP or UDP. ICMP works at the network layer and has no notion of sockets.

Re:Monitoring tiny web services by dgl on Sunday July 10, 2022 @12:33AM (#32041897)
The BSD socket API on many systems implements a raw socket type[1], so you can use the socket APIs to talk raw IP.

Some systems (Linux, Darwin) also implement a special icmp socket type which can allow unprivileged ping.

[1]: https://man7.org/linux/man-pages/man7/ip.7.html

Re:Monitoring tiny web services by oasisbob on Sunday July 10, 2022 @02:38AM (#32042384)
Regardless of what layer ICMP works at, its traffic is still transmitted using datagrams, and the call to do so is socket(), yes?

Are you just trying to point out the misnomer?