podoman

Thanks. To confirm, you'd like session replay for your react native / expo app?

We have an SDK request here: https://github.com/highlight/highlight/issues/4225

We don't have a particular leaning towards javascript, but haven't gotten to PHP yet. We're definitely open to contributors, but otherwise, we can hopefully get to this in the coming months.

Thanks. Frankly, the reason we have a separate fork is because some of our changes to rrweb in the early days were "hacky" to the say the least, and given that their team is part time on the project, there was occasionally a long cycle to get changes in.

We do have plans to consolidate one day, and I understand your sentiment about making diffs hard.

Fwiw, even beyond sponsoring the project, we even sponsored some folks on their team to work on particular features in the privacy and webgl space, so we have a really good relationship at this point.

I'll talk to the team regarding consolidating at this point. I appreciate the message.

That's a fun question. We don't necessarily have a common test case we run things against, but after big product launches, we do use Highlight to e.g. look at all sessions where a new feature is used.

One other thing that we have is an internal page that lets us simulate specific types of errors for debugging purposes. It looks like this: https://www.dropbox.com/scl/fi/0prnebmiip8huleaf1mub/Screen-...

Sorry about that. Do you mind "@"ing me in our discord? https://highlight.io/community

Or feel free to shoot me an email: jay [at] highlight [dot] io

Excited to get you going.

Excited for you to give it a try.

Everything we do is open source. Our roadmap, weekly tasks, etc.. So far, this has worked really well for us and made it easy for the community to be involved in what we're doing.

There are lots of fun challenges in front of us regarding incentivizing the community (bounties, etc..), as well as open sourcing more of our product processes. If you have any other pointed questions, happy to talk to them.

On session replay, clarity if definitely comparable to an extent. Keep in mind that the tool is very fine-tuned for a more marketing use case (w/ heatmaps, analytics, etc..). On the other hand, Highlight.io will monitor the content of network requests, trace request all the way to your backend, let you inspect the DOM, report on errors and much more.

Regarding the request features I mentioned above, we launched several features in this space today in our launch week: https://highlight.io/launch-week-2#day-2

We have considered that, the only problem is that its very hard to control session time as an end user. I.e. if you want to decrease the number of sessions coming through the platform, its more difficult if we're not counting by number of sessions.

This is something that we offer for enterprise companies, however.

One more thing to add here given your edit. Posthog does not directly compete with us. They have a session replay product; that is the only overlap. Nonetheless, their work on session replay (and in turn, with rrweb) is making the ecosystem better overall.

Great to hear. What don’t you like about the log flare and log push approach?

Opstrace was acquired by GitLab soon after launch. And signoz, in our minds is more leaning towards Grafana/Prometheus (and not particularly web app oriented).

I’m personally excited by the fact that there are other players in the space. It pushes us to move quickly and stay focused.

And I agree with your analysis, Datadog has proven that there’s a huge (and only growing) market for observability tooling.

Sounds good. Will work on some copy edits accordingly. Thanks for the feedback.

You’re correct. Maybe it should be called “application monitoring”? Any other ideas on verbiage?

Replay.io is a browser actually, so it’s for debugging web apps in development. highlight is a better fit for production web applications.

We definitely did take some inspiration there. I’ll add some attribution in the footer.

Yes. For your trial (first two weeks) you get unlimited usage. After that, you can explicitly set billing caps.

Let me know if that doesn’t answer the question.

Regarding redux recording, we've heard this occasionally, but it seems like the library (and proper state management libraries at large) is getting less popular nowadays. That being said, I think it would be cool if users could report data to the session to visualize it after the fact and we could use Redux as a first step in that direction.

I made a ticket here; do you mind helping with some of the points I added?

https://github.com/highlight/highlight/issues/5990

Regarding pricing, at that volume, we charge less than Logrocket (you'll need to reach out to us about it for now: jay [at] highlight [dot] io). We also have features that let you only record sessions with errors if you don't want to record everything. Overall, our goal from a business strategy is to be your one stop shop for application monitoring, not just a specialized tool for session replay like logrocket.

Sorry for the long reply.

In some cases, we'll sign a BAA. We handle this sort of thing on a case-by-case basis depending on risk. Feel free to shoot me an email if you have any particular questions in that space. jay [at] highlight [dot] io

Thanks for the kind words. Keep the feedback coming :)

Very cool demo. Highlight.io is a super visual tool and we've used that in demos and such as well!

Looks like Vadim beat me to it. Note what he said about running an OTEL collector. That's probably the best approach given they're onprem.

Yep. Very possible. You can send us logs via Fluent bit, Otel, and many other specifications. The easiest way to differentiate between logs would probably be to send a "service name" that's different between your servers.

If you'd like to ask questions synchronously or over email, I'm a jay [at] highlight [dot] io.

Appreciate the sentiment. Give us a try when you get a chance!

Thanks for sharing. Yeah, that’s a very reasonable use case to switch over. We have lots of logrocket and busgnag converts.

We do have more SDKs in the works, and occasionally, community members help us out as well (see the comment about our java sdk above). If you have any thoughts, please share (tickets below).

Regarding Elixir, we have some experience with the language within our team, so please reach out if we can build something for you in the short term. I'm at jay [at] highlight [dot] io.

https://github.com/highlight/highlight/issues/5082 https://github.com/highlight/highlight/issues/4452

I understand the sentiment. Maybe we can put something in our self hosting docs [1] that is more clear about how we think about our open source stance. In short, self hosting highlight is free on a single instance, but we charge for an “enterprise” deployment where we support managed infra, etc.

Are there any other things you’d suggest we can change on our site to make it bode better?

https://www.highlight.io/docs/general/company/open-source/ho...

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

we have a fly.io log shipper. docs here: https://www.highlight.io/docs/getting-started/backend-loggin...

> Also please make sure you have multi-line logs covered out of the gate. (Logtail, for example, doesn't support multiline stacktraces(!))

Noted. We're doing a push on our logging UX soon and can take a look.

> One thing that isn't clear to me from your marketing is what capability you have to support frameworks that aren't in your list. Do you have a regexp/generic parsing engine/ui?

I'm not entirely sure about the question, but we can receive logs via several specifications. OTEL, HTTP, Fluentbit, etc.. Does that answer your question? Or are you talking more about log filtering (i.e. filtering out logs for a specific log level)?

Appreciate the kind note.

We do consider sentry a competitor. There's a small bug on our site where our competitor page isn't rendering (taking a look).

There's a few reasons why someone would use us over Sentry. First is that our session replay product is much more robust imo, though they are working quickly in that space: https://www.highlight.io/docs/general/product-features/sessi...

Secondly, we have a logging product: https://www.highlight.io/docs/general/product-features/loggi...

And lastly, we prefer to keep our product simple and very opinionated. Most of our customers are using common frameworks and we're specifically focused on web. Long term, we see ourselves going in the direction of Datadog, building out a metrics and tracing product over the next 6 months or so.