Not sure what the difference is between that and Collect + Graphite / InfluxDB.
Introducing Vector: Netflix's On-Host Performance Monitoring Tool
51–60 of 64 posts
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#52It'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…
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#53It'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…
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#54After using Stackdriver for the last 18 months, I would never go back to rolling my own monitoring infra if I could avoid it. I had nagios, cacti, munin, graphite all running and had two ops guys pretty much 80% of their time managing it. Stackdriver with pagerduty and I have 250,000 custom metrics being published and hundreds and hundreds of graphs on dozens of dashboards. Although, I am looking at SignalFX to give…
Until I noticed the big red flag on the front page "Stackdriver is now part of Google."
Surely Google is going to kill this product and use the knowledge to offer something similar for Google's cloud services.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#55It'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…
The web was built, and runs on, *nix/BSD. Windows is an outlier. Windows can't even get the slashes going the right way. There's a reason 80% of internet traffic does not use Windows.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#56The charts look like they were built with nvd3. Can anyone confirm/deny?
That's right. Any suggestion of better reusable charts?
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#57It'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…
The web was built, and runs on, *nix/BSD. Windows is an outlier. Windows can't even get the slashes going the right way. There's a reason 80% of internet traffic does not use Windows.
I also don't think it's strictly true. For sure the underlying networking came from Unix. But as for the web itself, once we got to real dynamic content, it seems to me that Microsoft were the ones that got things moving.
While the Unix world was mired in the awful world of CGI, Microsoft gave us high-performance ISAPI, and then Cold Fusion (also on the Windows platform) and Microsoft's ASP made programming a little more sane. While the Unix world tried to deal with JSP (which IMHO wasn't a very good solution), the Microsoft platform seems to have been the innovators for several years, until Ruby on Rails and then node.js and stuff started coming out.
Today, the Apache server powers far more sites than any other, it's true. But IIS shares the 2nd-place spot [1]. When you say "There's a reason 80% of internet traffic does not use Windows", that's pretty much true for the servers, but far off the mark when counting clients. And the reason for that is that Microsoft's strength hasn't historically been radical advances, but in figuring out ways to take the bleeding edge tech that doesn't really work quite right yet, and packaging it into commodity software that may not be as sexy as envisioned by those with the original ideas, but actually useful to the average guy.
[1] http://www.zdnet.com/article/web-servers-microsoft-iis-and-n...
EDIT - missing word "world" in 3rd para
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#58After using Stackdriver for the last 18 months, I would never go back to rolling my own monitoring infra if I could avoid it. I had nagios, cacti, munin, graphite all running and had two ops guys pretty much 80% of their time managing it. Stackdriver with pagerduty and I have 250,000 custom metrics being published and hundreds and hundreds of graphs on dozens of dashboards. Although, I am looking at SignalFX to give…
Never heard of it, so checked out Stackdriver. Seemed very interesting, especially since it's geared at AWS (which we use). Until I noticed the big red flag on the front page "Stackdriver is now part of Google." Surely Google is going to kill this product and use the knowledge to offer something similar for Google's cloud services.
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#59Earlier 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?
Re: Introducing Vector: Netflix's On-Host Performance Monitoring Tool
#60I 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,…