11–20 of 64 posts
What 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.
I got down to you should be able to install PCP from binary packages made available by the PCP development team on: ftp.pcp.io and that threw up a red flag in my brain. Then I noticed that techblog.netflix.com doesn't redirect to https (and indeed can't serve https) (I use https://www.eff.org/HTTPS-EVERYWHERE and did not get content over https). The directions _I_ saw for building from source looked pretty innocuous,…
The charts look like they were built with nvd3. Can anyone confirm/deny?
Earlier 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?
Why not? Storage is cheap. Do you use something else to get historical visibility into metrics?
Am I wrong in saying this is a web interface that wraps PCP? So you can't really compare it to inspeqtor or collectd since those actually do the metrics collection.
Am I wrong in saying this is a web interface that wraps PCP? So you can't really compare it to inspeqtor or collectd since those actually do the metrics collection.
True. But that's the first release of Vector. We expect to make our custom PCP agents public soon.