3 ms·

Really nice and straightforward. Although I'm worried about the part where I'm supposed to install a service monitor on our servers. I know, many people alread

by bhaak 11y ago

Really nice and straightforward. Although I'm worried about the part where I'm supposed to install a service monitor on our servers. I know, many people already do stuff like that with airbrake or newrelic but I know that admins get grey hair because of that. :) You should think about offering an API where the client can upload its Gemfile.lock on their own.

phillmv 11y ago
That's the plan! We're going to be rolling that out in the next little while. If you want to get a personal email when it comes out, put "API" in the platform field in the email form on the link above.
pjungwir 11y ago
I thought that Airbrake and New Relic were supposed to support the ops team? I wouldn't want to run apps in production without them. I'm curious what admins object to?
- bhaak 11y ago
  Sending data from your server to a third party is something many people are not comfortable with. In environments with tighter security needs, this is outright verboten. It is true that those tools help the developers and the admins to monitor their products but where you aren't allowed to use them and have to run your own stuff, you might pay in higher maintenance costs.
peteforde 11y ago
I love how greybeards lose sleep over things perceived to be "not invented here" because there's a commercial entity behind it, but are completely fine with installing hundreds of open source tools by default that are often poorly audited because reasons.
- bhaak 11y ago
  The cases I have in mind are not because of NIH or because of greybeards' passed-down wisdom from the time when computers had to be carved out of stone. There are places where there are heightened security requirements (for various reasons[1]). Disallowing unnecessary outbound connections is a standard practice. This results in pruning quite a lot of possible attack vectors. [1] Of course some of those reasons are ridiculous. One place disallowed saving word documents as blobs in an Oracle database running on a Solaris server due to fear of malicious word document macros running on said server.

by bhaak 11y ago

phillmv 11y ago

That's the plan! We're going to be rolling that out in the next little while. If you want to get a personal email when it comes out, put "API" in the platform field in the email form on the link above.

pjungwir 11y ago

I thought that Airbrake and New Relic were supposed to support the ops team? I wouldn't want to run apps in production without them. I'm curious what admins object to?

bhaak 11y ago
Sending data from your server to a third party is something many people are not comfortable with. In environments with tighter security needs, this is outright verboten. It is true that those tools help the developers and the admins to monitor their products but where you aren't allowed to use them and have to run your own stuff, you might pay in higher maintenance costs.

peteforde 11y ago

I love how greybeards lose sleep over things perceived to be "not invented here" because there's a commercial entity behind it, but are completely fine with installing hundreds of open source tools by default that are often poorly audited because reasons.

bhaak 11y ago
The cases I have in mind are not because of NIH or because of greybeards' passed-down wisdom from the time when computers had to be carved out of stone. There are places where there are heightened security requirements (for various reasons[1]). Disallowing unnecessary outbound connections is a standard practice. This results in pruning quite a lot of possible attack vectors. [1] Of course some of those reasons are ridiculous. One place disallowed saving word documents as blobs in an Oracle database running on a Solaris server due to fear of malicious word document macros running on said server.