lukes386

7 ms·

1.
by lukes386 6y ago
Vector is designed to work well with systems like Kafka, not to replace them. While it does have a _very_ simple durable queue in the optional disk buffer feature, it is nowhere near the durability, fault tolerance, performance, etc of a fu
2.
by lukes386 6y ago
Yes, streaming k8s pod logs to Kafka and/or S3 is a great example of when you could use Vector. The "collect, transform, and route all your logs, metrics, and traces" bit is our most succinct explanation of what Vector does,
3.
by lukes386 6y ago
Thanks for pointing this out! That limitation is largely a holdover from when the Kafka sink was written and our support for accepting multiple data types was not as good as it is now. As things stand today, it should be a pretty simple cha
4.
by lukes386 6y ago
I only mentioned it briefly at the end of the post, but metamorphic testing is a very interesting technique that addresses exactly this [0]. The basic idea is to start with some known-good inputs and outputs, and then generate ways to modif
5.
A survey of testing techniques we've found useful(vector.dev)
98 points by lukes386 6y ago|22 comments
6.
by lukes386 7y ago
I've looked into OpenCensus/OpenTracing/OpenTelemetry (and the apparently unaffiliated OpenMetrics?) a bit, but I'm not as familiar as I'd like to be. It does seem like they're focused primarily on application-
7.
by lukes386 7y ago
Thanks for your interest! And please feel free to get in touch if you have any questions or feel there are things we could do to better support your use case: https://vector.dev/community/
8.
by lukes386 7y ago
Absolutely, Veneur is something we looked at quite a bit when it popped up. It's clear Stripe was feeling a lot of the same pain points we were when we started building Vector and they've come up with something really impressive.
9.
by lukes386 7y ago
Vector can act as a Splunk forwarder, but is designed to be much more flexible. In addition to forwarding to more storage systems (S3, Elasticsearch, syslog, etc), Vector can do things like sampling logs, parsing them, and aggregating them
10.
by lukes386 7y ago
We really love the idea of mtail and think it's criminally underused. A big part of the reason we started building Vector was to integrate that kind of functionality into a larger project, so people wouldn't have to get over the h
11.
by lukes386 7y ago
Thank you! Very glad it looks useful to you. It's still slightly rough around the edges, but Vector can actually ingest metrics today in addition to deriving metrics from log events. We have a source component that speaks the statsd pr
12.
by lukes386 7y ago
That's a good way to think about it! Heka was a big inspiration. The design isn't exactly the same, but we're aiming to solve a lot of the same problems.
13.
by lukes386 7y ago
Hi! I work on Vector. For a motivating example, let's say you have an application fronted by nginx. Using Vector would allow you to ingest your nginx logs off disk, parse them, expose status code and response time distributions to prom
14.
by lukes386 9y ago
https://github.com/carols10cents/rustlings
15.
by lukes386 10y ago
Yep, you're right, a plain FutureResult works fine in this case. I was aware of the general rule about boxing futures, but didn't realize it was unnecessary in this case. Thanks for pointing it out! I'll update the post.
16.
Getting Started with Tokio(lukesteensen.com)
166 points by lukes386 10y ago|21 comments
17.
by lukes386 13y ago
Interesting post, but that much scaffolding around the tests is a bit of a red flag to me. I personally try to move as much logic as possible into easily testable, independent methods. This leaves things like Rake tasks as very small, &quot
18.
by lukes386 13y ago
I've always wondered how difficult it would be to extract the vim "engine" into a library that could easily be reused by other programs. I can only assume the answer is "very difficult". Another idea would be some k
19.
by lukes386 13y ago
Yes, that's true. The approach has it's drawbacks though (validates_uniqueness_of being a prime example). As much as I like Rails, I sometimes wish it were designed with the database playing more of a role than just dumb storage.
20.
by lukes386 13y ago
On a somewhat related note, I'd love to see a more intermediate resource on how to really leverage PostgreSQL in your applications. As someone who primarily works with Rails, I feel like I use about 1% of PostgreSQL's power.
21.
A green threading library with true concurrency for Python(github.com)
30 points by lukes386 13y ago|39 comments
22.
by lukes386 13y ago
previous discussion here: https://news.ycombinator.com/item?id=5889477
23.
by lukes386 13y ago
Even easier would be to setup cloudflare in front of the site. All you have to do is set the cache control headers for your landing page to something like "max-age=300, public". That way cloudflare's servers will eat the vast
24.
by lukes386 14y ago
Just so you know, the "Give it a go" link in the README gives: An error has occurred: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
25.
WebGL Terrain Flyover Demo(zephyrosanemos.com)
303 points by lukes386 14y ago|116 comments
26.
Multi-core scaling: it’s not multi-threaded(erratasec.blogspot.com)
65 points by lukes386 14y ago|64 comments
27.
by lukes386 14y ago
Also cuisine[0], a more fully featured configuration management tools built on top of Fabric's lower level functions. [0]: https://github.com/sebastien/cuisine
28.
by lukes386 14y ago
I would also look at http://testling.com/ and https://saucelabs.com/ . Not sure which is best for this kind of testing, but those are two more I'm aware of.
29.
by lukes386 14y ago
Try http://ihackernews.com/
30.
by lukes386 14y ago
There's also a "scratch" plugin for vim that offers similar functionality: http://www.vim.org/scripts/script.php?script_id=664

More ›