3 ms·

The use case: you have more than a hundred machines emitting lots of monitoring data, much of which is uninteresting except in aggregate form. Instead of paying

The use case: you have more than a hundred machines emitting lots of monitoring data, much of which is uninteresting except in aggregate form. Instead of paying to store millions of data points and then computing the aggregates later, Veneur can calculate things like percentiles itself and only forwards those. It also has a separate, related purpose as a statsd protocol transport. You run it on the statsd port and it receives standard (or DataDog-extended) UDP traffic, then it forwards metrics via TCP to another backend. This has reliability benefits when operating over a network that might drop UDP packets, such as the public internet.

tchaffee 8y ago
Thanks. That's pretty good. Every README needs to start with something like this: "If you monitor applications, Veneur can save you money and increase reliability"
- mrkurt 8y ago
  That sounds like a startup's elevator pitch, not a README for an OSS project.
  - tchaffee 8y ago
    It kind of does sound like the first line of an elevator pitch, doesn't it? And as a programmer it helps me quickly decide if I should be care about it at all, and how to categorize it. Take a look at the software this "pipeline" is supposed to integrate with. It's a commercial product. Their landing page could not be clearer: "Modern monitoring & analytics. See inside any stack, any app, at any scale, anywhere" Perfect. Now I know what they do in plain English, how to mentally categorize their product, and even how to bookmark the page for the future when I might need their product. React is an OSS product, and it comes close "A declarative, efficient, and flexible JavaScript library for building user interfaces." Tells me an awful lot with only one jargon word: declarative. But I can still categorize it mentally and bookmark it even if I don't know what that words means. Make it easy for people to understand what you do, and you'll get more interest. People will bother to bookmark it. And maybe come back.

tchaffee 8y ago

Thanks. That's pretty good. Every README needs to start with something like this: "If you monitor applications, Veneur can save you money and increase reliability"

mrkurt 8y ago
That sounds like a startup's elevator pitch, not a README for an OSS project.
- tchaffee 8y ago
  It kind of does sound like the first line of an elevator pitch, doesn't it? And as a programmer it helps me quickly decide if I should be care about it at all, and how to categorize it. Take a look at the software this "pipeline" is supposed to integrate with. It's a commercial product. Their landing page could not be clearer: "Modern monitoring & analytics. See inside any stack, any app, at any scale, anywhere" Perfect. Now I know what they do in plain English, how to mentally categorize their product, and even how to bookmark the page for the future when I might need their product. React is an OSS product, and it comes close "A declarative, efficient, and flexible JavaScript library for building user interfaces." Tells me an awful lot with only one jargon word: declarative. But I can still categorize it mentally and bookmark it even if I don't know what that words means. Make it easy for people to understand what you do, and you'll get more interest. People will bother to bookmark it. And maybe come back.