rsdbdr203

I disliked a lot of things about working at Meta, the monorepo was not one... it was truly amazing, and very well done.

I was very impressed by Scuba's ability to ingest and search data... and very unimpressed by the interface. I found it terribly unintuitive, and often didn't get you what you wanted without having to run multiple queries.

Phabricator was pretty sweet... and the internal version of mercurial was a dream!

This isn't a great argument... sure, Splunk "saved the day" because it caught that really bad security thing... but what other tools, at half the cost, could have also "saved the day"? If most of them could have, then it's not really worth the price... right?

100% this... profit, or it's not worth it

>Their feature flagging system was also on point.

Which one... there are like 3 (or more)? The ones I worked with were the single biggest cause of SEVs. I wrote some tooling around trying to make it better, but it honestly needed to be completely replaced.

>Workplace is a fantastic replacement of Wiki that surfaces relevant & interesting content to you.

Yea? I found it horrible to have to read through post-after-post-after-post to try and keep up-to-date with what's going on. Not my way of ingesting information.

>Their chat tools are way better than Google Chat / Microsoft Teams (not sure how it stacks up against Slack since I'm not a huge user of them).

100% disagree... telling my dog to bark at the neighbor because I want something from them is better than Workplace chat. Constantly switching between internal beta and production to try and get the features I wanted, with something stable. Go ahead and send me a link to that message in a chat... oh yea, you can't :-|

This is exactly why I build log-store. Can easily handle 60k logs/sec, but I think more importantly is the query interface. Commands to help you extract value from your logs, including custom commands written in Python.

Free through '23 is my motto... Just a solo founder looking for feedback.

The interface (GUI) is OK (and looks better than mine honestly), but the usability isn't great. The query syntax is tough to grok IMO. Using the sample dataset it took myself and a friend who knew Kibana like 5 minutes to figure out how to make a pie chart of the various OS types. It's probably that we're just dense and don't know what we're doing, but with log-store you just click the pie chart icon next to the field, and it will update the query and render the chart. I think that's easier to use.

Only binary. Ultimately I would like to sell it, but just looking for feedback at the moment.

Thanks! Would love to know more about your experience running Splunk... Can I reach out to you?

Looking for some small niche... Industrial, automotive, even garbage truck monitoring :-) I'm not looking to build a massive public company or anything either... More a lifestyle business. We'll see.

I guess I misread your comment... my apologies. What I'm building is more a replacement for Splunk: on-prem log analytics. As you point out, it is not compatible w/Elasticsearch in any way.

I've been working on one: log-store.com It has a DB built-in that is schema-less, but it's really the frontend I've been trying to focus on, as I think the interface to Kibana is poor.

That's _exactly_ what I'm trying to build, and you don't have to pay anything. I was frustrated with what I thought was a poor interface for Kibana, and having to deal with schema for Elasticsearch, so I built log-store. I appreciate any feedback!