3 ms·

Preface: I was not asked to write this and these are my own experiences with Highlight As someone building a bootstrapped product with my co-founder [1][2] Hig

by Syntaf 3y ago

Preface: I was not asked to write this and these are my own experiences with Highlight As someone building a bootstrapped product with my co-founder [1][2] Highlight has been a pretty amazing time save for us; setting up session replaying + monitoring + logging took all of 15 minutes and let me get back to actually focusing on building the product. We're running on DOKS (Digital Ocean K8s) due to my familiarity with the hosting stack, and I really didn't want to spend the time setting up a cluster agent + log rotation strategy. Surprisingly, the popular logging providers out there today don't really have alternative quick-start solutions for shipping logs in clusters, but Highlight DID and it also came with error monitoring + session replays. All in all I'm pretty happy with the product and looking forward to using it more as we approach our product's soft-launch date at the end of this month with some select clubs. [1] https://embolt.app/ https://embolt.app/ [2] https://demo.embolt.app/admin/ https://demo.embolt.app/admin/

podoman 3y ago
Thanks for the kind words, we’re glad our approach to observability resonates!
e12e 3y ago
> Surprisingly, the popular logging providers out there today don't really have alternative quick-start solutions for shipping logs in clusters, but Highlight DID and it also came with error monitoring + session replays. Where did you find this? Did you self-host or go with hosted? On the docs for ingesting data, I only found some guides for things like aws - not k8s? And there's just some Docker guides and an open issue regarding hosting: https://github.com/highlight/highlight/issues/4390 https://github.com/highlight/highlight/issues/4390 Looking forward to dependencies being cut down a bit as it should make it almost trivial to set it up for k8s (both hosting and ingesting logs).
- Syntaf 3y ago
  We're using the hosted option, and since we run on rails all we needed was the ruby SDK [1]. Essentially, we just have an additional logger attached to our stdout logger which ships logs over to highlight using their OpenTelemetry implementation. No infrastructure required, pretty simple. [1] https://www.highlight.io/docs/getting-started/backend-sdk/ruby/rails https://www.highlight.io/docs/getting-started/backend-sdk/ru...
  - e12e 3y ago
    Ah, I interpreted your comments as if you had automated logging from all k8s nodes/pods to go to highlight via some kind of automation like a sidecar or something (ie not just specific application logs).
- vadman97 3y ago
  > Looking forward to dependencies being cut down a bit as it should make it almost trivial to set it up for k8s (both hosting and ingesting logs). We're planning to support k8s (openshift etc.) in the next 3-6 months. If you have another platform you'd like to see supported, please commented on the issue you linked.
el_nahual 3y ago
Hijacking your thread a bit, but I have to give you feedback on your landing page copy. I don't understand what you sell! I thought you were an app for people that care about their social media reach (like, twitter tech influencers). Forgiveable since your hero copy is " Build your Reach". It's super important when writing marketing copy to name your users. If I'm a club chair for the local bowling league and I see "sports leagues" mentioned then my brain will just think "oh, this is for me!" The first paragraph in your about page is so much better: > Whether you're a sports club, social group, hobbyist organization, or non-profit, embolt is the solution to running your organization. We believe every club and organization should have a reliable platform to accept online member dues, manage registration, run events, and so much more. I would replace the hero copy with a condensed version of that.
- Syntaf 3y ago
  Thanks for your feedback! I agree with what you're saying, our homepage came before our product so we're in a goofy stage of having a nearly finished MVP product and no mention or links to it on the marketing pages.

by Syntaf 3y ago

podoman 3y ago

Thanks for the kind words, we’re glad our approach to observability resonates!

e12e 3y ago

> Surprisingly, the popular logging providers out there today don't really have alternative quick-start solutions for shipping logs in clusters, but Highlight DID and it also came with error monitoring + session replays. Where did you find this? Did you self-host or go with hosted? On the docs for ingesting data, I only found some guides for things like aws - not k8s? And there's just some Docker guides and an open issue regarding hosting: https://github.com/highlight/highlight/issues/4390 https://github.com/highlight/highlight/issues/4390 Looking forward to dependencies being cut down a bit as it should make it almost trivial to set it up for k8s (both hosting and ingesting logs).

Syntaf 3y ago
We're using the hosted option, and since we run on rails all we needed was the ruby SDK [1]. Essentially, we just have an additional logger attached to our stdout logger which ships logs over to highlight using their OpenTelemetry implementation. No infrastructure required, pretty simple. [1] https://www.highlight.io/docs/getting-started/backend-sdk/ruby/rails https://www.highlight.io/docs/getting-started/backend-sdk/ru...
- e12e 3y ago
  Ah, I interpreted your comments as if you had automated logging from all k8s nodes/pods to go to highlight via some kind of automation like a sidecar or something (ie not just specific application logs).
vadman97 3y ago
> Looking forward to dependencies being cut down a bit as it should make it almost trivial to set it up for k8s (both hosting and ingesting logs). We're planning to support k8s (openshift etc.) in the next 3-6 months. If you have another platform you'd like to see supported, please commented on the issue you linked.

el_nahual 3y ago

Hijacking your thread a bit, but I have to give you feedback on your landing page copy. I don't understand what you sell! I thought you were an app for people that care about their social media reach (like, twitter tech influencers). Forgiveable since your hero copy is " Build your Reach". It's super important when writing marketing copy to name your users. If I'm a club chair for the local bowling league and I see "sports leagues" mentioned then my brain will just think "oh, this is for me!" The first paragraph in your about page is so much better: > Whether you're a sports club, social group, hobbyist organization, or non-profit, embolt is the solution to running your organization. We believe every club and organization should have a reliable platform to accept online member dues, manage registration, run events, and so much more. I would replace the hero copy with a condensed version of that.

Syntaf 3y ago
Thanks for your feedback! I agree with what you're saying, our homepage came before our product so we're in a goofy stage of having a nearly finished MVP product and no mention or links to it on the marketing pages.