I'm curious how this compares to Zabbix's agent and server. Does PCP give you finer grained details, or is it possibly more lightweight?
Introducing Vector: Netflix's On-Host Performance Monitoring Tool
21–30 of 64 posts
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#22The charts look like they were built with nvd3. Can anyone confirm/deny?
That's right. Any suggestion of better reusable charts?
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.
For reference here's what I made: http://forrestthewoods.com/unbalanced-design-of-super-smash-...
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#23Earlier quoted context omitted.
If its not collecting and persisting metrics, is it more of a glorified htop?
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...
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#24Where can I find deb packages for pcp version 3.10 or higher?
See http://pcp.io/docs/installation.html#deb or direct link at ftp://ftp.pcp.io/projects/pcp/download/deb/ - but I only see packages for i386 arch, so you may have to compile from source if on amd64 or other architecture.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#25Wow this looks great, thanks for releasing it! Nice to see even 'simple' stuff like this that can help people who aren't running at Netflix scale is still released.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#26Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#27It's enormously frustrating to me that the Windows platform is so far behind.
I've been researching for a rebuild of our ecommerce site with the idea of a modern microservice architecture. Team skillset and some other considerations dictate a .Net environment.
Netflix and other companies have created a really rich platform, between logging and monitoring technologies like this; message queueing; deployment; and so on. In the Windows environment there's precious little to compare to.
One bright spot is the news story also on HN today [1] about MS announcing Docker-related Hyper-V technology - but in the next version of Windows server.
It might be that to satisfy those .Net compatibility wishes, we just go to Mono and do everything else in Linux.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#28Where can I find deb packages for pcp version 3.10 or higher?
The git repo has a MakePkg script that will generate deb packages for you.
I found it really easy to use.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#29Not sure what the difference is between that and Collect + Graphite / InfluxDB.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#30What does this have that CloudWatch enhanced metrics doesn't? From the screenshots, the metrics look pretty similar. Not a slight at all against this project (it looks awesome), I'm just curious if your infrastructure is already AWS based what would cause you to choose a non-CloudWatch option.
It looks like it has some metrics that aren't present in cloudwatch without a lot of scripting, such as Memory utilization. I'm new to cloud watch though, so someone please correct me if that is wrong.