Curious if there are any plans to have a “client only” package available? We’re looking at migrating to Sensu for our monitoring needs. However we don’t like the idea of having to install the server, api etc. on all our clients.
Thanks
Andrew
Hey Andrew,
Can you elaborate on your hesitation to have the source code for the server and api in addition to the client on multiple servers?
The server and API only need to be run on a single server. The code is open source and publicly available, so it can’t be ‘compromised’, and it only takes up a few hundred kilobytes. Pragmatically, different components share some code that would be extraneous overhead to abstract and package each component separately.
-Nick
···
On Thursday, August 15, 2013 3:23:23 PM UTC-7, geek...@temporalspaces.com wrote:
Curious if there are any plans to have a “client only” package available? We’re looking at migrating to Sensu for our monitoring needs. However we don’t like the idea of having to install the server, api etc. on all our clients.
Thanks
Andrew
Is this the reason why using the Chef monitor cookbook it installs even init-scripts for api and dashboard too…? Nothing activates those, but it´s a bit unclean for a client to be monitored only…
Sincerely,
Iiro Niinikoski
···
On Friday, August 16, 2013 7:05:05 PM UTC+3, Nick Stielau wrote:
Hey Andrew,
Can you elaborate on your hesitation to have the source code for the server and api in addition to the client on multiple servers?
The server and API only need to be run on a single server. The code is open source and publicly available, so it can’t be ‘compromised’, and it only takes up a few hundred kilobytes. Pragmatically, different components share some code that would be extraneous overhead to abstract and package each component separately.
-Nick
On Thursday, August 15, 2013 3:23:23 PM UTC-7, geek...@temporalspaces.com wrote:
Curious if there are any plans to have a “client only” package available? We’re looking at migrating to Sensu for our monitoring needs. However we don’t like the idea of having to install the server, api etc. on all our clients.
Thanks
Andrew
We could make the Sensu package not manage files outside of /opt/sensu. Currently, /etc/init.d/sensu-*, /etc/sensu, and /usr/share/sensu are put in place to make it easy to get started.
···
On Sun, Mar 16, 2014 at 11:17 AM, Iiro Niinikoski iiro.niinikoski@gmail.com wrote:
Is this the reason why using the Chef monitor cookbook it installs even init-scripts for api and dashboard too…? Nothing activates those, but it´s a bit unclean for a client to be monitored only…
Sincerely,
Iiro Niinikoski
On Friday, August 16, 2013 7:05:05 PM UTC+3, Nick Stielau wrote:
Hey Andrew,
Can you elaborate on your hesitation to have the source code for the server and api in addition to the client on multiple servers?
The server and API only need to be run on a single server. The code is open source and publicly available, so it can’t be ‘compromised’, and it only takes up a few hundred kilobytes. Pragmatically, different components share some code that would be extraneous overhead to abstract and package each component separately.
-Nick
On Thursday, August 15, 2013 3:23:23 PM UTC-7, geek...@temporalspaces.com wrote:
Curious if there are any plans to have a “client only” package available? We’re looking at migrating to Sensu for our monitoring needs. However we don’t like the idea of having to install the server, api etc. on all our clients.
Thanks
Andrew