leeab

6 ms·

1.
by leeab 1y ago
I've heard of AWS Neuron...didn't realize they had a package called NeuronX. Tbh, I feel like many AI companies have similar names. Maybe the guys who own neuronx.io might be more concerned...
2.
by leeab 1y ago
We're not for nor against Slurm. I do believe it has use cases in HPC, scientific and academic settings. We think our web UI is a bit easier to use and we do offer a competing scheduler. Our focus is definitely more on container-first,
3.
by leeab 1y ago
Well, it depends on how many GPU clouds you're managing. We've talked to a bunch of companies, some startups, some enterprises and the main trend we found was the sheer number of companies with GPU clusters from multiple clouds...
4.
by leeab 1y ago
We collect a handful of metrics, but coming from our previous lives in DevOps, we only collect just what's needed to avoid unnecessary metrics bloat. The main 3 are: - GPU runtime stats from NVIDIA smi - Running pods from Kube state -
5.
by leeab 1y ago
Someone asked about this earlier. We have considered this and may go down this route in the future. Was there something specific that you were looking for with open source? (ie: privacy, cost, etc) Our solution is self-hosted and your data
6.
by leeab 1y ago
Ahh yes...here’s how you solve that. Just install the Neurox Control plane onto any regular Kubes cluster (doesn’t need GPUs, just needs persistent storage. ie: EKS, AKS, GKE, etc) without that last flag in the instructions: `--set workload
7.
by leeab 1y ago
One of the reasons we went down the self-hosted route is to ensure that your data remains on your servers. Since our architecture allows for separation between where our control plane lives vs where GPU workloads run, we can definitely host
8.
by leeab 1y ago
We have considered this and may go down this route in the future. One thing we asked ourselves was what open sourcing provides. Usually it's a desire for privacy or cost in the form of self-hosting, among other reasons. Currently, our
9.
by leeab 1y ago
Haha...there is some truth to that. We do use Prometheus under the hood to collect metrics. However, our thesis is that metrics alone isn’t enough. We marry metrics + kube state + cost data to get the whole picture. Also we're purpose
10.
Show HN: Neurox – GPU Observability for AI Infra(github.com)
25 points by leeab 1y ago|22 comments
11.
by leeab 1y ago
GPU observability is broken, so we built Neurox. When I co-founded Mezmo (a Series D observability platform), we obsessed over logs, metrics, and traces. I learned firsthand how critical app-level observability is for DevOps, cutting throug
12.
by leeab 6y ago
As a founder, these are the top 3 things I wish someone had told me about balancing cost and scalability. For other YC founders out there, are these the same things you struggled with?
13.
by leeab 9y ago
Sounds good! Yeah our site is definitely in need of some love. Just haven't had time (busy plugging tech debt and working on new stuff). Planning on major improvements next month along with onboarding.
14.
by leeab 9y ago
Just created a live example: https://logdna.com/frame_tester.html The gif was from our docs page which afaik doesn't allow js.
15.
by leeab 9y ago
Hi everyone, I'm a co-founder / CTO of LogDNA. We were in Y Combinator's W15 batch and launched our cloud logging platform last year ( https://news.ycombinator.com/item?id=11074537 ) From the beginning, we’ve a
16.
Show HN: LogDNA – Embed server logs onto any web page(docs.logdna.com)
37 points by leeab 9y ago|7 comments
17.
by leeab 9y ago
Congratulations on the launch!! LogDNA is proud to be a part of the Manifold journey. Can't wait to see what's in store next!
18.
by leeab 10y ago
Awesome! And definitely let us know if we can improve in any way.
19.
by leeab 10y ago
Thanks JJ! Yeah, we hope to earn your Kubernetes business :)
20.
by leeab 10y ago
Hmmm this may have been a bug. It should show stderr as err. Let me look into this.
21.
by leeab 10y ago
Yeah one of those mysteries of life. :/ One day we'll probably go back and try this on a few older versions to see if we can repro what happened. But yeah, it was right off the bat when we started our beta, 2 different people said
22.
by leeab 10y ago
Awesome! We're pretty responsive on Intercom as well if you run into issues post install. But definitely share your feedback if you notice areas that can be improved.
23.
by leeab 10y ago
Yes that's true for many things in Kubernetes but not as frequent in the logging space for Kubernetes. Many still rely on Fluentd as a parsing filter first to extract metadata like pod name or container name. And most of the logging on
24.
by leeab 10y ago
Ahh yes, thanks for catching that. I just made a note that we collect from all namespaces currently. Yeah, we now set our agent up w/o namespaces. During our beta, we originally had it set up inside `kube-system` but 2 of our testers m
25.
by leeab 10y ago
:) Hope you'll give us a shot. And let us know what you think!
26.
by leeab 10y ago
We currently treat each line separately and we can maintain line ordering okay. We have thought about this before and doing something like: if a line starts with tab or a fixed number of spaces a few times in a row, treat it as 1 line with
27.
by leeab 10y ago
Hi everyone, I'm a co-founder / CTO of LogDNA. We were in Y Combinator's W15 batch and launched our cloud logging platform last year ( https://news.ycombinator.com/item?id=11074537 ) Based on user feedback, we&
28.
Show HN: LogDNA – Set up Kubernetes logging with 2 kubectl commands(github.com)
76 points by leeab 10y ago|23 comments
29.
by leeab 10y ago
Hey! Lee here (CTO / co-founder) wanted to say thanks for all the feedback when we launched in February. We're constantly adding new features weekly and if there's anything we can help with, I'm happy to answer any quest
30.
by leeab 11y ago
Not yet. We're still figuring our what's needed for this. It seems there's no auditing requirement at all.

More ›