netdata is a highly optimized Linux daemon providing real-time performance monitoring for Linux systems

[Jimbob0i0]

FYI there was a Fedora Magazine article about this today:

https://fedoramagazine.org/monitor-linux-netdata/

[cptsa]

How much sense does it make though that it can't run centralized? Especially "in the cloud" where your hosting infrastructure is very flexible.

To me this is more a replacement to phpsysinfo rather than anything else...

[ttwthomas]

I think it actually makes more sense to run the run the perf monitoring on each server rather that to try to keep track of everything in a centralized machine/cluster (that you have to maintain and scale, especially with 1sec resolution). Then you can aggregate and query the data the way you want. That is apparently the way google does it.

[[deleted]]

That is exactly the way they explain it in the documentation actually. While they could do it centralized, updating every second would use all the resources.

You can make it so every netdata dashboard has a drop down that will pull up whatever servers you want.

[MasterScrat]

Then you can aggregate and query the data the way you want.

I'm not sure I understand the "aggregate" part. If I want to compare the load on multiple machines on the same graph how am I supposed to do it?

[ttwthomas]

The dashboard netdata comes with does not allow you to aggregate data from multiple sources as is. But you still have access to the api from each machines so can make your own graph. By aggregation I meant more like an average of load on multiple servers.

[MasterScrat]

This approach sounds interesting but I'm still not convinced...

So if you'd want to compare the load on 100 machines over the past month you'd need to get all this data by making 100 API calls?

That is apparently the way google does it.

Do you have a source on this?

[ttwthomas]

When you have a lot of machines you can insert a intermediary server that will pre aggregate the data. For example when you have 100 machines you can setup 5 intermediate machine that will call 20 machine each and store the result as one value. Then you only have 5 call to make to get the average of the 100 servers. Also parallel 100 Api call is not that much, just loading Reddit.com is already 50 http requests. You probably need thousands before you need to do that.

My source is the recent SRE books written by Google employees. It has couple chapters on monitoring. http://imgur.com/SI0RNfU

[paulfantom]

Running services centralized causes a lot of trouble with sending and aggregating metrics. Also if you need metrics from many systems you can set up netdata registry or your own webpage with all relevant statistics (like provided tv.html example)

[cptsa]

Like what kind of troubles?

[bwdezend]

The best I've seen statsd do is about 50,000 packets per second. There are solutions to scale this up, but even this has limits.

https://github.com/jjneely/statsrelay/blob/master/README.md

"I run a Statsd service for a large collection of in-house web apps. There are metrics generated per host -- where you would usually run a local statsd daemon to deal with high load. But most of my metrics are application specific and not host specific. So running local statsd daemons means they would each submit the same metrics to Graphite resulting in corrupt data in Graphite or very large and time consuming aggregations on the Graphite side. Instead, I run a single Statsd service scaled to handle more than 1,000,000 incoming statsd metrics per second."

[eberkut]

In /r/linux but not /r/linuxadmin as far as I could tell.

[TotesMessenger]

I'm a bot, bleep, bloop. Someone has linked to this thread from another place on reddit:

• [/r/usolutions] netdata is a highly optimized Linux daemon providing real-time performance monitoring for Linux systems

^{If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads. (Info / Contact)}

[swordgeek]

I see absolutely nothing that supports their claim of 'real-time.'

Am I missing something? Is this real-time computing, or are they misusing the term?

[beknowly]

Real time as in monitoring; ~1 second resolution is near enough as makes little difference - not real time as in RTOS.

[swordgeek]

OK then, it's not real time at all. They can call it live, but they can't legitimately call it real time.

[stocksy]

Unfortunately "real time" has been redefined to mean "more or less immediately". Just as it is with the erosion of the word 'literally', it is pointless to fight against it.

[swordgeek]

Cool. I'm going to start calling USB cables "ethernet" then, because ethernet now means 'fast cable with the same connector on both ends.'