text stringlengths 0 1.17k |
|---|
• App.net's paid model and its potential success |
• The importance of network size and user engagement in social media platforms |
• Paid vs free models in social media and their impact on user engagement |
• The concept of a sponsored podcast and a job search platform (Hired.com) |
• Contributions and user engagement on the Sidekick platform |
• The use of the Go programming language in the Inspector tool and its potential impact on user engagement |
• Comparison of Inspector and Sidekick as open-source projects |
• Design decisions made for the Inspector tool, including removing unnecessary features and adding modern functionality |
• The importance of integrating application components with the operating system's init system for reliability and maintenance |
• The developer's experience with integrating components with an init system |
• Removal of features from the inspector, including monitoring file permissions and directory permissions |
• Simplification of the configuration process for the inspector |
• Installation story for the inspector, including distribution through package cloud and package repositories |
• Comparison of the open-source and pro versions of the inspector |
• The developer's experience learning the Go programming language and rewriting the inspector code multiple times |
• Challenges and frustrations with learning Go and idiomatic coding practices |
• The speaker discusses the choice of Go as a programming language for their project, Inspector, and how it offers simplicity and a strong standard library. |
• The speaker compares Go to Ruby, noting that Ruby is better suited for large-scale applications and prototyping, while Go excels at building small, focused projects. |
• Inspector, a monitoring tool, is discussed, and its features, including daemon-specific metrics, host metrics, and integration with popular collaboration tools, are mentioned. |
• The speaker notes that the open-source version of Inspector is still in its early days, but it will monitor any service integrated with the init system, and users can contribute their own daemon-specific metrics. |
• The speaker discusses the advantages of using Go, including its simplicity, strong standard library, and low runtime dependencies. |
• Inspector provides real-time monitoring and alerting for metrics, with a console-based interface |
• Commercial version (Pro) supports monitoring init d, legacy systems, and has additional features |
• Pro version includes features such as chat room integration for alerts, ownership management, and customizable alerting |
• New features being considered for the open-source version, including monitoring cron jobs and a web interface for metric overview |
• Roadmap and engagement opportunities for users to contribute to the project's development and launch |
• Agenda is not an issue and the speaker is open to help and improvement |
• The speaker has a list of features but wants to add more and gather ideas |
• Specific feature to add more application components to the inspector |
• PRs (pull requests) are encouraged to add more features |
• Show notes will include links to the code and company site |
• Sponsors mentioned: Code Ship, hired.com, and Digital Ocean |
• The speaker thanks the audience and says goodbye |
[0.00 --> 14.46] welcome back everyone this is the changelog and i'm your host adam stekowiak this is episode |
[14.46 --> 21.34] 130 jared and i talked to mike parham he's back again just like sidekick he's got inspector now |
[21.34 --> 28.48] another open source slash pro version of software out there for you to use this one is application |
[28.48 --> 33.20] infrastructure monitoring reimagined it's called inspector now let me talk about that we also |
[33.20 --> 38.60] talked about other fun ways he's making money as a open source developer so great conversation there |
[38.60 --> 44.96] we've got some awesome sponsors for this show code ship hired.com and digital ocean we'll tell |
[44.96 --> 49.90] you a bit more about hired.com and digital ocean later in the show but our friends at code ship |
[49.90 --> 54.62] is a hosted continuous deployment service that just works you can easily set up continuous |
[54.62 --> 59.34] integration for your application in just a few steps and automatically deploy all your code |
[59.34 --> 64.80] when your tests pass code ship has great support for lots of languages test frameworks as well as |
[64.80 --> 69.84] notification services they integrate with github and bitbucket and can deploy your code to cloud |
[69.84 --> 76.72] services like heroku aws nojitsu google app engine or even your own servers setup takes just three |
[76.72 --> 82.52] minutes get started today with their free plan and make sure you use our code the changelog podcast |
[82.52 --> 89.66] again that code is the changelog podcast and you will get a 20 discount for three months on any |
[89.66 --> 94.10] plan you choose head to codeship.io and now on to the show |
[94.10 --> 102.34] welcome back everyone we're uh we're joined here with a guest that's no uh stranger to the show mike |
[102.34 --> 107.32] param and mike you're also not a stranger to the changelog we've covered all sorts of stuff that you've |
[107.32 --> 114.20] done over the years everything from dolly to sidekick to launchy um launchy lunchy i'm not sure |
[114.20 --> 119.98] if i which it's launchy launchy i think we pronounce it's spelled launchy though right yeah it is yeah |
[119.98 --> 126.76] there's already a gym called launchy so i couldn't i couldn't squat on that name right so i'm here mike's |
[126.76 --> 133.86] here jared's here jared say hello hey we uh we've been waiting to i think maybe about a month or two to |
[133.86 --> 138.32] to have this conversation you've been working on something brand new so maybe the best way to start |
[138.32 --> 144.40] would be to just you know get you know tell us what's going on what you do brand now sure um for |
[144.40 --> 148.46] the last four months i've been working on a top secret project uh which i just announced yesterday |
[148.46 --> 156.68] and it's called inspector um it's my fresh take on application infrastructure monitoring |
[156.68 --> 164.40] uh that is to say all the moving parts of of a server-side application um a little tool which |
[164.40 --> 169.54] allows you to monitor all those those moving parts to make sure everything is healthy and if anything |
[169.54 --> 177.10] looks out of the ordinary inspector will immediately send out alerts to uh to where you wherever you have |
[177.10 --> 184.82] configured to say hey this doesn't look right uh so it's really helpful in terms of uh just you don't |
[184.82 --> 189.86] have to watch a dashboard all day or something like that you just you know watch your inbox and |
[189.86 --> 197.52] and if something shows up that then you know to investigate so inspector comes into a space that's |
[197.52 --> 203.38] you know has uh some offerings i think you're no stranger to that as sidekick of course famously um |
[203.38 --> 211.78] was you know rescue um you know done right or done better um inspector has competition with |
[211.78 --> 220.70] monit with god with uh what's the python one um uh supervisor d yeah so there's a few others |
[220.70 --> 226.98] blue pill was one i was thinking of so there's there's other players in this space what's inspector's |
[226.98 --> 233.04] unique take and what's the value add there right so you know if you if you know anything about monit |
[233.04 --> 241.32] uh it's it's pretty obvious that that monit is the main yeah um the main influence in the way |
[241.32 --> 247.10] inspector works uh i've used monit for the last five years and i've just always been frustrated |
[247.10 --> 252.64] with some of its quirks and so i i really wanted to build for the last few years i really wanted to |
[252.64 --> 260.76] build something that was like sort of a monit plus plus or or my take on monit and so as i as i |
[260.76 --> 264.62] really got serious about doing this a few months ago i i really started looking at the monit feature |
[264.62 --> 272.22] set and and just sort of what did i want uh in terms of um you know my previous job was |
[272.22 --> 277.98] director of infrastructure or director director of technical operations whatever you want to call it |
[277.98 --> 283.18] but basically if the site had problems i i was the guy who had to whose head was on the line |
[283.18 --> 291.54] um so this kind of tool uh was critical for for my job i had to know when something was was acting up |
[291.54 --> 299.38] uh so so yeah i mean i went through uh monit monit's feature set and pared down all the different |
[299.38 --> 304.72] features that i thought were not useful uh from an application monitoring point of view |
[304.72 --> 312.98] and added new features that i thought were critical that monit didn't have and and so that's that's what |
[312.98 --> 321.20] became inspector um inspector has makes some interesting choices in terms of its design that some people |
[321.20 --> 328.76] aren't going to necessarily like for instance well it doesn't monitor init d legacy init d services |
[328.76 --> 336.00] really and that's by choice um part of application monitoring is i'm trying to |
[336.68 --> 342.92] guide people on how to build a reliable application right inspector is going to tell you if something is |
[342.92 --> 350.74] not not working reliably but it also wants to guide you to build better applications |
[350.74 --> 357.48] and part of that is using a proper modern init system like upstart like systemd like run it |
[357.48 --> 366.82] and so uh init d one of the problems with init d is you there's no sort of central demon that you can |
[366.82 --> 374.48] query for the status of a process or a service um and everything's kind of rolled into this just big |
[374.48 --> 381.24] hairy bash script in etsy and etsy and so when i realized this a couple months ago i realized that |
[381.24 --> 386.80] this was a sort of a a decision point in the design here that was going to be fundamental to the way |
[386.80 --> 396.36] inspector works so do i want to support this legacy um ball of mud or do i want to make a hard stop here |
[396.36 --> 405.36] and and ask people hey or or guide people or try to educate people about why this is a problem and and and it's not that |
[405.36 --> 412.80] hard to learn the new the new systems and and thereby get a more reliable uh setup for your application components |
[412.80 --> 420.34] so that's that's kind of what i did i was gonna say the um so just to kind of give the the listeners |
[420.34 --> 424.90] who listen to this to kind of a maybe a an outline of what we think this show might be about this time |
[424.90 --> 430.28] uh in traditional fashion of the changelog we want to go deep we want to figure out all the details of |
[430.28 --> 435.06] inspector but i think a neat part of this transition for you which you had said this you you didn't want |
[435.06 --> 439.80] to um you had to make a choice of uh supporting that ball of what was your word |
[439.80 --> 448.86] ball of mud um so you had to make this choice of of doing that or something else and um episode 92 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.