vadman97

9 ms·

61.
by vadman97 4y ago
Absolutely, makes sense. We'll make sure to make all security features we ship a first-class citizen of the open source version and available to all customers.
62.
by vadman97 4y ago
With the highlight.io client, we use an opt-in strategy to be privacy-first (since network request bodies + headers are often sensitive). We're not capturing network requests/responses unless you enable it and allow deeply configu
63.
by vadman97 4y ago
Yup, planning to have a Ruby/Rails SDK shipped next week. We're also working on docs on our opentelemetry usage to make it easy for folks to contribute to future ones. Here's the github issue if you'd like to add any con
64.
by vadman97 4y ago
Performance and ease-of-use of ClickHouse have been great so far! Looking forward to be leaning more in on ClickHouse for the logging product ( https://www.highlight.io/docs/general/product-features/loggi... )
65.
by vadman97 4y ago
That's great feedback; understood. What features would you consider "enterprise" in that case? Right now, nothing is paywalled in our self-hosted version, and we're still very much in the brainstorming phase here.
66.
by vadman97 4y ago
That's a great point! Just opened a PR to fix this: https://github.com/highlight/highlight/pull/4362 Switching this to https too since the our rrweb fork is now public (ssh reference was previously neces
67.
by vadman97 4y ago
Following up regarding the other points I missed. Compared to OpenReplay, we have similar functionality in our session replay, but we've focused a lot of effort on making a cohesive error monitoring (backend and frontend) experience. W
68.
by vadman97 4y ago
Hey! Sure thing. Our frontend session replay happens in two parts: 1. The HTML DOM Recording using rrweb ( https://github.com/rrweb-io/rrweb ) 2. The monkey patching of fetch, xhr, console methods, combined with data fro
69.
by vadman97 4y ago
We've put a lot of effort already to make the OSS setup a single `docker compose` command despite the extensive infra we use under the hood. Longer term, we're planning to support other deployment strategies such as kubernetes, cl
70.
Publishing a TS monorepo to NPM is hard(highlight.io)
2 points by vadman97 4y ago|0 comments
71.
by vadman97 4y ago
Data ingest challenges mounted quickly with a synchronous pipeline. Check out how we added Apache Kafka to help relieve our woes!
72.
Is Kafka the Key? The Evolution of Highlight's Ingest(highlight.io)
5 points by vadman97 4y ago|2 comments