Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Follow-up on "Linux server monitoring tools"

aarvik.dk

Post reply on HN
Print view View original

1–10 of 23 posts

Re: Follow-up on "Linux server monitoring tools"

#2

Post by wpietri »

From the description of linux-dash:

> It is easily extensible from its architecture which just calls the php exec() function and sends it to an ajax request.

I presume the network police have already revoked somebody's license to run a server, yeah?

Re: Follow-up on "Linux server monitoring tools"

#3

Post by adionditsak »

wpietri wrote: post #2

From the description of linux-dash: > It is easily extensible from its architecture which just calls the php exec() function and sends it to an ajax request. I presume the network police have already revoked somebody's license to run a server, yeah?

Well, i did not write it! I just tested it :-) But that is how it is build. It came on HN same time as my post. Here it is: https://news.ycombinator.com/item?id=7125153

Re: Follow-up on "Linux server monitoring tools"

#4

Post by zimbatm »

Widening the net a bit but since you added network-connected monitoring, check out sensu. It's backward-compatible with nagios plugins and handles cloud systems very well (no need to restart the server every time a host is being added/removed). It's also capable of extracting system metrics and forward them to graphite/... . Really great tool.

And just for metrics, collectd is great too.

Re: Follow-up on "Linux server monitoring tools"

#5

Post by adionditsak »

wpietri wrote: post #2

From the description of linux-dash: > It is easily extensible from its architecture which just calls the php exec() function and sends it to an ajax request. I presume the network police have already revoked somebody's license to run a server, yeah?

I also believe that exec() is not dangerous if you use it right, and if your www-data/apache-user do not got any sudo rights to risk someone to take advantage of your machine. This have been proved from various sources, if i know right. I understand it can be a security hole if you let the user write anything, but this is eg. not the case with Linux-dash.

Re: Follow-up on "Linux server monitoring tools"

#6

Post by adionditsak »

zimbatm wrote: post #4

Widening the net a bit but since you added network-connected monitoring, check out sensu. It's backward-compatible with nagios plugins and handles cloud systems very well (no need to restart the server every time a host is being added/removed). It's also capable of extracting system metrics and forward them to graphite/... . Really great tool. And just for metrics, collectd is great too.

Nice zimbatm, i will definitely take a look at those :-) Sounds great with Nagios + cloud systems integration.

Re: Follow-up on "Linux server monitoring tools"

#7

Post by dijit »

adionditsak wrote: post #5
wpietri wrote: post #2

From the description of linux-dash: > It is easily extensible from its architecture which just calls the php exec() function and sends it to an ajax request. I presume the network police have already revoked somebody's license to run a server, yeah?

I also believe that exec() is not dangerous if you use it right, and if your www-data/apache-user do not got any sudo rights to risk someone to take advantage of your machine. This have been proved from various sources, if i know right. I understand it can be a security hole if you let the user write anything, but this is eg. not the case with Linux-dash.

local shell is as good as root as far as I'm concerned.

especially if that machine is single purpose, which most of mine are.

Re: Follow-up on "Linux server monitoring tools"

#8

Post by btgeekboy »

adionditsak wrote: post #5
wpietri wrote: post #2

From the description of linux-dash: > It is easily extensible from its architecture which just calls the php exec() function and sends it to an ajax request. I presume the network police have already revoked somebody's license to run a server, yeah?

I also believe that exec() is not dangerous if you use it right, and if your www-data/apache-user do not got any sudo rights to risk someone to take advantage of your machine. This have been proved from various sources, if i know right. I understand it can be a security hole if you let the user write anything, but this is eg. not the case with Linux-dash.

SELinux if left enabled (as it should be...) will help mitigate the risks. But root access often isn't necessary to totally screw you. For example, adding a machine to a botnet does not require root, nor does accessing the data for your application (such as databases and local files owned/manipulated by your apache user).
Post reply on HN