Introducing Vector: Netflix's On-Host Performance Monitoring Tool
techblog.netflix.com
Introducing Vector: Netflix's On-Host Performance Monitoring Tool
1–10 of 64 posts
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#2Anyone care to compare this to something like collectd? https://collectd.org/
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#3Anyone care to compare this to something like collectd? https://collectd.org/
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.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#4What 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.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#5Anyone care to compare this to something like collectd? https://collectd.org/
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.
If its not collecting and persisting metrics, is it more of a glorified htop?
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#6What 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.
CloudWatch charges you per instance if you want 1 minute metrics instead of the standard (free) 5 minute metrics. Any tool that collects the data for you gets you out of that $3.50/instance/month detailed monitoring charge [1].
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#7Earlier quoted context omitted.
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.
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.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#8I got down to
you should be able to install PCP from binary packages made available by the PCP development team on:
ftp.pcp.io
The directions _I_ saw for building from source looked pretty innocuous, but you might see a different set of directions if you're being MITMed. Observe an appropriate amount of caution.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#9Anyone care to compare this to something like collectd? https://collectd.org/
[deleted]
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#10Earlier quoted context omitted.
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.
If its not collecting and persisting metrics, is it more of a glorified htop?
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.