And yeah OpenTelemetry is where lots of the industry is going and so are we. You can already do cool things with us and the collector but we plan on automating a lot and expand on that.
We totally agree our website is way too wordy and we are working on explaining our vision through various ways. Screenshots of course, but also things like short videos. We actually just did one of our quickstart https://youtu.be/XkVxYaHsDyY. It’s not perfect but we will get there:-)
Yes that is frustrating indeed. On top of paying your external vendor, you are punished by the egress cost you have to pay to your infrastructure cloud provider. This is one of the problems we wanted to solve. Feel free to contact me seb@opstrace.com.
Yes! We will be having features that you have to pay a subscription for. It starts with the usual suspects: custom SSO, custom domains, and authorization - things that we would be hosting as an ongoing service for customers. Most features will be open when we create them -- this is near and dear to our hearts -- it’s important our users can be successful with the OSS version. Over time, the commercial features will also flow into the open as we release new proprietary ones. Our commercial features will be public in our repo, under a commercial license.
We will also have a managed version where we deploy and maintain it for the customer in a cloud account they provide us.
We are still experimenting with pricing and what can be open and closed. To be completely transparent we chose custom domains because we know companies care a lot. When we have more features on the commercial side we can start to chat about supporting it in the open version. Still early in our journey, happy to discuss anything, like a small plan with just custom domains. Would you pay for that?
Yeah. That’s kind of what I mean. I have no problem paying some money to support you guys and not have to host it on my own. I generally prefer my monitoring etc to not be done by myself anyway cause I take myself offline way too often
Only point was of there was going to be a smaller plan for homelabs or the like that doesn’t have the raw amount of Traffic or features as the enterprise plans do.
I (generally) like taking myself offline. Thats how I learned everything I know (by fucking up). But thats also why I like to have my mail/monitoring outside my own selfhosted infrastructure. Cause those two things are something that should be running 100% of the time. And if I dont feel like fixing whatever I broke right this moment, I like to feel like I dont have to.
Sometimes I just go to bed whenever I broke something and fix it tomorrow. If I have to flick my light switches by hand until then, so be it, I can live with that. But mail and monitoring cant wait that long :P
Nobody said we gave up on continuous integration. Quite the contrary! We use jenkins and other CI tools on a daily basis.
Once we have tools to build debian packages easily in a controlled environment (containers), the CI server will be able to use the same tools to build and test the final package. The advantage here is that a developer can test the whole workflow and build local test/dev packages with the same tools and environment as the CI server.
...and so have the compression and filtering tech, I'm sure. If you strip out most attachments, the average email message is incredibly tiny when gzipped.
