Not Node.JS specifically, but just npm for dependencies and task running to build the React client from source. If you're not looking to build the client from source, the distributed client bundle should suffice and only Python is required.
Honestly? Just write your own SVG code. If you inspect the elements the output data is super simple and easy to understand. NVD3 just wraps D3.js which just wraps utilities that output relatively basic data. Well, d3js is a data-binding system that's way too god damned complicated if all you want to do is make some simple charts which is how it's used 99% of the time.
I've spent more time trying to manipulate chart libraries into doing almost the same thing but just different enough to cause pain and suffering. Output your own path data and it's a million times easier.
His concerns seem plain to me. Unauthenticated channels for software distribution or software installation instructions are bad.
The techblog isn't using SSL, and the git pull url for PCP is using the git protocol which is also unauthenticated, rather than the authenticated https transport (ssh is only an option when user accounts make sense).
Someone's at a conference and follows the link over public wifi. They get the same page but with "here's how to get PCP: ftp evil.io or git clone git://git.evil.io/pcp" Even if the webpage were ssl-enabled so that an attacker can't rewrite the pcp.io links, an attacker or evil network operator could MITM git.pcp.io or ftp.pcp.io. (FTP?!)
Being in Ubuntu's repo doesn't make it safe if Ubuntu's maintainers have no (semi-)trustworthy way of getting the code.
Goal is a bit different. Vector doesn't collect and persist metrics. We needed something that had as little overhead as possible so it could be deployed to all our hosts and simplify the process of analyzing those metrics.
Not really. htop doesn't visualize historical trends from numerous sources at the same time. Vector also allows us to interface with other metric sources, beyond /proc.
doesn't htop require you to go onto the box? We haven't released our custom pcp modules yet which allow more complex visualizations such as flamegraph generation from perf event sampling.
Yes, exactly - htop is a curses application that shows instantaneous samples of a few system metrics, but it mostly lists processes - this is nothing like Vector at all...
I think the reason is they have a bunch of ephemeral hosts which they don't want to put in a central web interface or collect statistics on.
They are only interested in getting some insight as to what went wrong with this host so they can fix it in the future.
pcp is happy to collect & persist metrics; vector just doesn't happen to render them. pcp offers other ways to interact with live or archive-saved data, including other webapps.
Neither does collectd, it just gathers and transmits the data to an endpoint you specify. It's also quite lightweight (once you address the memory leaks, at least).
