Hey HN. We’re Jay and Vadim from Highlight.io (<a href="https://highlight.io">https://highlight.io</a>). We’re building an open source [1] monitoring platform for web applications.<p>Today we’re excited to be sharing a performance tool we’ve been working on, which helps you inspect the latency of code execution from the client to the server.
As engineers at past startups, we often had to debug slow queries, poor load times, inconsistent errors, etc... While tools like Jaegar [2] helped us inspect server-side performance, we had no way to tie user events to the traces we were inspecting. In other words, although we had an idea of what API route was slow, there wasn’t much visibility into the actual bottleneck.<p>This is where our performance product comes in: we’re rethinking a tracing/performance tool that focuses on bridging the gap between the client and server.<p>What’s unique about our approach is that we lean heavily into creating traces from the frontend. For example, if you’re using our Next.js SDK, we automatically connect browser HTTP requests with server-side code execution, all from the perspective of a user. We find this much more powerful because you can understand what part of your frontend codebase causes a given trace to occur. There’s an example here [3].<p>From an instrumentation perspective, we’ve built our SDKs on-top of OTel, so you can create custom spans to expand highlight-created traces in server routes that will transparently roll up into the flame graph you see in our UI. You can also send us raw OTel traces and manually set up the client-server connection if you want. [4] Here’s an example of what a trace looks like with a database integration using our Golang GORM SDK, triggered by a frontend GraphQL query [5] [6].<p>In terms of how it's built, we continue to rely heavily on ClickHouse as our time-series storage engine. Given that traces require that we also query based on an ID for specific groups of spans (more akin to an OLTP db), we’ve leveraged the power of CH materialized views to make these operations efficient (described here [7]).<p>To try it out, you can spin up the project with our self hosted docs [8] or use our cloud offering at app.highlight.io. The entire stack runs in docker via a compose file, including an OpenTelemetry collector for data ingestion. You’ll need to point your SDK to export data to it by setting the relevant OTLP endpoint configuration (ie. environment variable OTEL_EXPORTER_OTLP_LOGS_ENDPOINT [9]).<p>Overall, we’d really appreciate feedback on what we’re building here. We’re also all ears if anyone has opinions on what they’d like to see in a product like this!<p>[1] <a href="https://github.com/highlight/highlight/blob/main/LICENSE">https://github.com/highlight/highlight/blob/main/LICENSE</a><p>[2] <a href="https://www.jaegertracing.io" rel="nofollow">https://www.jaegertracing.io</a><p>[3] <a href="https://app.highlight.io/1383/sessions/COu90Th4Qc3PVYTXbx9Xee7xbQqN?ts=5.243&network-resource-id=25">https://app.highlight.io/1383/sessions/COu90Th4Qc3PVYTXbx9Xe...</a><p>[4] <a href="https://www.highlight.io/docs/getting-started/native-opentelemetry/overview">https://www.highlight.io/docs/getting-started/native-opentel...</a><p>[5] <a href="https://static.highlight.io/assets/docs/gorm.png">https://static.highlight.io/assets/docs/gorm.png</a><p>[6] <a href="https://github.com/highlight/highlight/blob/1fc9487a676409f12fb84709603dcdf0b4440952/backend/main.go#L218-L266">https://github.com/highlight/highlight/blob/1fc9487a676409f1...</a><p>[7] <a href="https://highlight.io/blog/clickhouse-materialized-views">https://highlight.io/blog/clickhouse-materialized-views</a><p>[8] <a href="https://www.highlight.io/docs/getting-started/self-host/self-hosted-hobby-guide">https://www.highlight.io/docs/getting-started/self-host/self...</a><p>[9] <a href="https://opentelemetry.io/docs/concepts/sdk-configuration/otlp-exporter-configuration/#otel_exporter_otlp_endpoint" rel="nofollow">https://opentelemetry.io/docs/concepts/sdk-configuration/otl...</a>