text
stringlengths
0
1.17k
[3040.02 --> 3046.80] right you know x y or z and those kind of sites are super valuable why did you pick go over you know
[3046.80 --> 3053.36] your your bread and butter that's a good question so um so blue pill and god are both written in ruby
[3053.36 --> 3064.78] um so i i have always used monet and shied away from them because to me a monitoring package needs to
[3064.78 --> 3074.16] be as robust and as simple as humanly possible for reliability purposes and i don't want my
[3074.16 --> 3080.46] application written in the same stack that is monitoring it it's that's a you know you've got
[3080.46 --> 3086.18] possibility of them both dying for some for some reason you know if your ruby's vm somehow breaks
[3086.18 --> 3094.60] well now your monitoring solution breaks too um i always loved the monet simplicity you know the fact
[3094.60 --> 3098.86] that it only used a couple megabytes of memory uh the fact that it was just a single binary
[3098.86 --> 3107.70] to start and uh and so i wanted that type of simplicity in in inspector what i didn't want to
[3107.70 --> 3114.94] do is write it in c or c plus plus so when something like go or rust came along i said well these are
[3114.94 --> 3120.70] perfect next generation system languages that i can use to build this type of infrastructure
[3120.70 --> 3127.24] without having to deal with um you know memory management and pointers and all that kind of
[3127.24 --> 3133.16] stuff directly so uh that's why i that's why uh that's one of the reasons i did it and go the other
[3133.16 --> 3140.16] reason i did it and go is it's simply because the language has a really strong standard library where
[3140.16 --> 3148.76] i didn't need to pull in any third party packages at all to implement it so uh inspector has no
[3148.76 --> 3154.86] runtime dependencies aside from the linux the linux kernel you know it's just a single but it doesn't
[3154.86 --> 3163.52] even use libc so you think that choice has paid off so far well we'll see um i have you know at the
[3163.52 --> 3169.68] very least i've invested in learning go and become a uh not a beginner go programmer anymore but you know
[3169.68 --> 3176.64] i'd say a journeyman go programmer um so in terms of investing in myself you know it's paid off
[3176.64 --> 3182.74] but uh you know there's uh it remains to be seen how how well the commercial product sells and how
[3182.74 --> 3189.78] well the open source project is is taken up you know it's still early days having been launched 24 hours
[3189.78 --> 3196.64] ago it's it's often that um whenever you try something new like this whenever you go from ruby to go
[3196.64 --> 3202.02] that you often compare can you give us a comparison of uh what you love about both or what you love more
[3202.02 --> 3208.02] about ruby or what you love more about go now that you're um experiencing the the awesomeness that it
[3208.02 --> 3218.72] is sure um ruby is fantastic for building a big thing if you can leverage like rails you know you just
[3218.72 --> 3225.88] you really can't beat building a website in rails it's still it's still the best thing out there as far
[3225.88 --> 3232.04] as i'm concerned i would not want to build a large website and go i think that would be inappropriate
[3232.04 --> 3241.02] i think the the ruby flexibility and prototyping speed is still um much faster than goes speed
[3241.02 --> 3246.36] where go shines is where you've got something very simple very focused that you want to build
[3246.36 --> 3254.50] and you can you know sort of hold the code in your head and just build it out really quick um you know
[3254.50 --> 3263.28] go's speed is it goes runtime speed is really um really nice for sure uh running my test suite you
[3263.28 --> 3268.52] know takes tenth of a second you know of course ruby can do some of that if you if you structure the
[3268.52 --> 3274.08] code correctly but but yeah i think i think ruby has points where it shines in terms of these
[3274.08 --> 3280.06] frameworks like rails like sidekick where you can build these large-scale apps pretty quickly
[3280.06 --> 3287.68] and uh and go is more of a sort of a sharp focus tool for building uh you know smaller lower level
[3287.68 --> 3294.98] things is typically how i think of it in your uh in your list mentioning uh the introduction to
[3294.98 --> 3298.54] inspector you've got several things that you you kind of have on the plate that you're that you're
[3298.54 --> 3303.64] supporting in terms of like writing alerts to slack hip chat campfire flow doc some of the
[3303.64 --> 3310.00] common hit lists of of popular kind of collaboration tools you also mentioned that it's brand new
[3310.00 --> 3316.26] it's not 1.0 yeah can you talk about um since it's since this is new and for those listening
[3316.26 --> 3321.00] you're probably listening as much as maybe five days after the recording of this so when we say
[3321.00 --> 3324.96] it was released one day ago it was actually like six days ago technically depending upon when you
[3324.96 --> 3331.98] listen to this but um can you talk a bit about you know this early version not 1.0 version um
[3331.98 --> 3337.74] in terms of feature set which you've put in it and like maybe where you see things going and
[3337.74 --> 3346.04] and possibly even how um how how actually using go supports some of the the the lifespan you see for
[3346.04 --> 3355.06] this so the uh the base inspector the open source version of inspector uh will monitor any any
[3355.06 --> 3361.58] service that's integrated with your init system uh it will monitor daemon specific metrics so it'll it
[3361.58 --> 3367.64] knows it understands my sequel it understands nginx redis memcached those are the four i launched
[3367.64 --> 3373.72] with i see there are tons of opportunity to for people to contribute their own daemon specific
[3373.72 --> 3381.16] metrics uh things like um cassandra kafka you know there's a there's a whole world of like java
[3381.16 --> 3386.44] infrastructure for instance that isn't covered at all but i'd love to have integration with just
[3386.44 --> 3393.14] more infrastructure that people use to build their apps those happen to be the four things that i use
[3393.14 --> 3399.72] um that the ruby community uses often but um you know maybe python folks maybe uh for instance like
[3399.72 --> 3407.46] celery or or rabbit mq uh would be more examples so daemon specific metrics are in the open source
[3407.46 --> 3413.90] version uh what else is there so you're gonna you're gonna monitor your your cpu and your memory of
[3413.90 --> 3421.50] your process your daemon specific metrics you can monitor the host metrics things like swap disk space usage
[3421.50 --> 3429.48] cpu usage and then oh you can also you can also get an overview of all the status of all the services that
[3429.48 --> 3436.46] it's inspecting at a given moment and you can also see a graph of a metric in the console so if you're if
[3436.46 --> 3442.88] you're at the terminal and something uh an alert fires you can actually see the history of the metric right in
[3442.88 --> 3448.00] your console without having to open up and find a graph or something like that which is pretty nice
[3448.00 --> 3457.10] uh now in terms of uh uh the commercial version pro pro has the ability to monitor init d the old
[3457.10 --> 3463.34] legacy stuff that ball of mud that i referred to um that's so you you didn't want to do it but you'll
[3463.34 --> 3470.82] do it for money exactly exactly i like that that's a good one jared well that's that's a that's an
[3470.82 --> 3477.18] example where if people have legacy services if they're an enterprise and and they just don't want to
[3477.18 --> 3483.34] touch the thing but they do want to use uh inspector to monitor you you pay the money and the problem is
[3483.34 --> 3488.72] solved um yeah i mean part of part of this hard line that i'm having to take with features is trying to
[3488.72 --> 3495.04] guide people to to author better applications and sometimes that means i you know i'm not going to
[3495.04 --> 3500.42] support the old way of doing something because i really genuinely feel it's not the right way to do
[3500.42 --> 3506.00] things now if people want to pay me money to so that they continue continue to do it the old way
[3506.00 --> 3512.26] then that's that's their choice but you know i'm i'm taking a stand here and saying that init d is not
[3512.26 --> 3520.00] the right thing to do anymore um so uh yeah so init d is supported in pro um and then yeah as you said
[3520.00 --> 3526.88] chat rooms for teams who want alerts to be piped into their shared chat room where maybe they've got
[3526.88 --> 3531.82] people in the chat room 24 7 that's a perfect example where you can sort of cut down noise in
[3531.82 --> 3540.20] your inbox by by directing uh the alerts into the chat rooms and then uh the final feature in pro right
[3540.20 --> 3547.40] now is the uh ownership so you can give ownership to various components you can say i want alerts for
[3547.40 --> 3553.40] this thing to go to this particular team or this particular person because inspector itself the open
[3553.40 --> 3561.08] source version you can only send alerts to a single email address that's it now what's coming down
[3561.08 --> 3566.26] the pipe uh yeah i've got a bunch of ideas one thing i want to put in the open source version
[3566.26 --> 3574.18] is monitoring cron jobs to ensure that cron jobs are running uh if you have a cron job that runs hourly
[3574.18 --> 3581.40] and you deploy your code and that code change breaks that cron job how do you know
[3581.40 --> 3588.22] oftentimes the job will just start silently failing and you won't know until a customer calls
[3588.22 --> 3593.40] customer emails or maybe you don't receive a report the next day or something like that
[3593.40 --> 3602.44] but having having something that that that notifies what i want to do is have a way for the cron job to
[3602.44 --> 3608.36] notify inspector that hey i just ran and then inspector will say if i haven't received a notification within
[3608.36 --> 3614.68] the last hour or within the last day to fire off an alert to say hey this cron job didn't fire
[3614.68 --> 3622.08] let me just say as as a longtime monet user and relatively happy monet user if you do that feature
[3622.08 --> 3627.26] i will immediately switch i was gonna say you seem like you're lamenting with the pain like i can almost
[3627.26 --> 3632.14] audibly hear the pain you felt from not having that feature yeah i've looked for solutions there's
[3632.14 --> 3638.12] some online services where you can uh you know do your cron job and then you know do ampersand ampersand
[3638.12 --> 3643.92] and then hit some api that just says i did it right that it actually succeeded and then they'll send you
[3643.92 --> 3650.68] emails and stuff if it fails um tried those there's other you know things where you can just pipe it to
[3650.68 --> 3657.44] an email address if it fails anyways they all suck right well mine's gonna suck right mine's gonna suck
[3657.44 --> 3667.06] just as much oh oh well yeah so in a better way though maybe yeah so so that was one idea i had for
[3667.06 --> 3672.44] another feature um you know the other obvious feature would be sort of a web interface to see an
[3672.44 --> 3678.62] overview of the different metrics you're tracking and to see pretty graphs um yeah that that would
[3678.62 --> 3685.28] probably be a pro a pro um feature i'm not sure uh but yeah anything that's sort of team or
[3685.28 --> 3692.96] collaborative is definitely uh going to be lean toward pro things like cron jobs though you know i can
[3692.96 --> 3699.58] see individuals wanting those as part of their applications and so putting a cron job checker uh
[3699.58 --> 3707.20] seems like a natural fit yeah i'm for it cool i'll count that as a plus one on the issue then
[3707.20 --> 3715.90] there you go well cool mike um we uh we tend to ask a few questions at the end of the show but