code logs -> 2020 -> Sat, 17 Oct 2020< code.20201016.log - code.20201018.log >
--- Log opened Sat Oct 17 00:00:11 2020
00:24 Kindamoody is now known as Kindamoody[zZz]
01:51 catalyst [catalyst@Nightstar-ahaorv.dab.02.net] has quit [Ping timeout: 121 seconds]
02:00 catalyst [catalyst@Nightstar-i9fqgj.dab.02.net] has joined #code
02:53
<@sshine>
so when you're building REST services, is there a standard way to have a 'ping' endpoint? I'm thinking for monitoring services that check if the REST service is responding.
03:04
<&[R]>
If you have authentication, I'd use the "whoami" point
03:12 Degi [Degi@Nightstar-de55ug.pool.telefonica.de] has quit [Ping timeout: 121 seconds]
03:13 Degi [Degi@Nightstar-81kocn.pool.telefonica.de] has joined #code
03:22
<@sshine>
[R], I don't have anything yet. the guy who is running the pings isn't so experienced with DevOps, so I thought I'd look around for standards.
03:23
<&[R]>
Well, you could throw up a static file, but all that'd serve to show is the httpd is working
03:24
<&[R]>
So you'd want a check that intrisically does something (so that it doesn't eventually get replaced by a static file by some well-intentionned refactoring), but ideally also something that doesn't do anything horribly complicated either
03:24
<@sshine>
this is an application server, so I was thinking simply 'GET /ping' => { "running": true }, even though that does not say if 'POST /derp' also works and responds in reasonable time. so perhaps the best ping service is one that mocks server usage. my last job, however, had some kind of standard for detecting that the service simply hadn't died.
03:25
<&[R]>
Maybe something that produces status output (like is the database connection up/down)
03:25
<@sshine>
this is for automated monitoring, by the way.
03:26
<&[R]>
Though, I should mention I don't work with REST APIs at all
03:27
<&[R]>
Just RPC ones
03:27
<@sshine>
translating "status output" into my domain: it sounds like what I want is to run the service and see that it still returns consistent output. the /ping endpoint can be faked, but /compile with { "contract": "transfer(X, Y)", "blockchain": "evm" } probably won't /accidentally/ give the right answer...
03:27
<@sshine>
yeah okay, I appreciate the response.
03:28
<@sshine>
I was wondering if there were a standard ping schema for some kind of monitoring software that people tend to like.
03:28
<@sshine>
maybe something that reports latency.
03:29
<&[R]>
/time
03:29
<&[R]>
Return a UNIX timestamp
03:38 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed]
03:38 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
03:40
<@sshine>
nice! :)
03:41
<&[R]>
If it's JS, you can do `(new Date) - 0` and get milliseconds in there too
03:42
<@sshine>
oh, ha. nah, it's Haskell.
04:12 Yossarian [soryu@Nightstar-d7h8ki.org] has left #code ["WeeChat 2.8"]
04:39 mac [macdjord@Nightstar-re5.7if.45.45.IP] has joined #code
04:39 mode/#code [+o mac] by ChanServ
04:42 macdjord [macdjord@Nightstar-re5.7if.45.45.IP] has quit [Ping timeout: 121 seconds]
04:49 macdjord|slep [macdjord@Nightstar-re5.7if.45.45.IP] has joined #code
04:49 mode/#code [+o macdjord|slep] by ChanServ
04:52 macdjord|slep is now known as macdjord
04:52 mac [macdjord@Nightstar-re5.7if.45.45.IP] has quit [Ping timeout: 121 seconds]
05:14 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed]
05:14 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
05:32 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed]
05:32 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
05:41 celticminstrel [celticminst@Nightstar-r1cum5.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
05:42 celticminstrel [celticminst@Nightstar-r1cum5.dsl.bell.ca] has joined #code
05:42 mode/#code [+o celticminstrel] by ChanServ
05:46 celticminstrel [celticminst@Nightstar-r1cum5.dsl.bell.ca] has quit [Ping timeout: 121 seconds]
06:30 [R] [rstamer@genoce.org] has quit [[NS] Quit: No Ping reply in 180 seconds.]
06:34 mac [macdjord@Nightstar-re5.7if.45.45.IP] has joined #code
06:34 mode/#code [+o mac] by ChanServ
06:35 macdjord [macdjord@Nightstar-re5.7if.45.45.IP] has quit [Ping timeout: 121 seconds]
06:50 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed]
06:50 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
07:12 [R] [rstamer@Nightstar-d7h8ki.org] has joined #code
07:13 mode/#code [+ao [R] [R]] by ChanServ
07:14 Yossarian [soryu@Nightstar-d7h8ki.org] has joined #code
07:25 Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has joined #code
07:25 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
07:26 Pinkhair [uid208117@Nightstar-h2b233.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
08:18 catalyst_ [catalyst@Nightstar-d8k1h5.dab.02.net] has joined #code
08:22 catalyst [catalyst@Nightstar-i9fqgj.dab.02.net] has quit [Ping timeout: 121 seconds]
08:37 mac is now known as macdjord|slep
08:42 Yossarian [soryu@Nightstar-d7h8ki.org] has quit [[NS] Quit: WeeChat 2.8]
08:42 Yossarian [soryu@Nightstar-d7h8ki.org] has joined #code
09:52 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code
09:54 catalyst_ [catalyst@Nightstar-d8k1h5.dab.02.net] has quit [Ping timeout: 122 seconds]
10:17 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [Ping timeout: 121 seconds]
10:17 catalyst [catalyst@Nightstar-d8k1h5.dab.02.net] has joined #code
10:24 Kindamoody[zZz] is now known as Kindamoody
10:25 catalyst_ [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code
10:26 catalyst [catalyst@Nightstar-d8k1h5.dab.02.net] has quit [Ping timeout: 121 seconds]
11:01 Reiver [quassel@Nightstar-ksqup0.co.uk] has quit [[NS] Quit: Reblooting.]
11:18 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has joined #code
11:58 catalyst_ is now known as catalyst
12:42 celticminstrel [celticminst@Nightstar-r1cum5.dsl.bell.ca] has joined #code
12:42 mode/#code [+o celticminstrel] by ChanServ
14:53 Reiver [quassel@Nightstar-ksqup0.co.uk] has joined #code
14:53 mode/#code [+ao Reiver Reiver] by ChanServ
15:04 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
15:04 mode/#code [+qo Vornicus Vornicus] by ChanServ
15:20 Kindamoody is now known as Kindamoody|afk
15:50 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed]
15:51 VirusJTG_ [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
16:37 bluefoxx [fuzzylombax@Nightstar-gmbj85.vs.shawcable.net] has quit [Ping timeout: 121 seconds]
17:04 Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
17:07 ErikMesoy [Bruker@Nightstar-5d8uau.bb.online.no] has quit [[NS] Quit: Leaving.]
17:12 ErikMesoy [Bruker@Nightstar-5d8uau.bb.online.no] has joined #code
17:12 mode/#code [+o ErikMesoy] by ChanServ
19:04 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [Connection closed]
19:12 macdjord|slep is now known as macdjord
19:26 Pinkhair [uid208117@Nightstar-h2b233.irccloud.com] has joined #code
21:32 bluefoxx [fuzzylombax@Nightstar-gmbj85.vs.shawcable.net] has joined #code
22:07 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
22:50 Kindamoody|afk is now known as Kindamoody
23:43 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code
--- Log closed Sun Oct 18 00:00:13 2020
code logs -> 2020 -> Sat, 17 Oct 2020< code.20201016.log - code.20201018.log >

[ Latest log file ]