Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vadman97
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
by
vadman97
3y ago
The hardest errors to group / tag are ones that are further removed from the actual error cause (think frontend bug that causes a bad request that then causes a backend error, or an OOM because of a gradual memory leak). For these, we&
32.
▲
by
vadman97
3y ago
Both - tagging errors into broad buckets can help with filtering and searching for categories of errors, while finding similar errors surfaces ones that might be more familiar to an unknown one. We're learning as we go though and also
33.
▲
Show HN: Using LLMs and Embeddings to classify application errors
(github.com)
11 points
by
vadman97
3y ago
|
6 comments
34.
▲
by
vadman97
3y ago
Have you seen the OTEL auto instrumentation package[1]? It supports a number of common frameworks (as middleware) and libraries (via monkeypatches) setting up spans for you to capture things like external http requests, database/cache
35.
▲
by
vadman97
3y ago
Clarity is meant for high level analytics around product usage, while Highlight is built for engineering observability (catching and debugging errors). Highlight offers network tracing, log ingest (both client and server side), and error mo
36.
▲
by
vadman97
3y ago
This would be more involved as you'd need to run and configure the infra dependencies yourself. For every container listed in the compose file [1], you'd want to set up that service. After that, you can use the shell scripts refer
37.
▲
by
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 an
38.
▲
by
vadman97
3y ago
Yes, a good number of folks have come from those tools. Not only to consolidate tools, but to get a cohesive debugging experience (see the frontend session and the server side errors + logs all in one place).
39.
▲
by
vadman97
3y ago
Appreciate it. Let us know what you think when you have a chance to try it!
40.
▲
by
vadman97
3y ago
Highlight can monitor server-side web apps; I'm assuming that's what you're running on those servers? I'd suggest instrumenting the common application code with our backend SDKs and deploying that change to all on-premis
41.
▲
by
vadman97
3y ago
Mind asking in our Discord community ( https://highlight.io/community )? Happy to help there - looks like you are missing the docker compose v2 plugin ( https://docs.docker.com/compose/ ).
42.
▲
by
vadman97
3y ago
Mind trying https://discord.gg/SEJEfSqctQ ?
43.
▲
by
vadman97
3y ago
Do you mind joining our Discord ( https://highlight.io/community ) and asking there? Happy to help over a DM once you are in.
44.
▲
by
vadman97
3y ago
Our JS SDK provides a strict privacy mode that obfuscates the entire DOM for this use-case (see more here: https://www.highlight.io/docs/getting-started/client-sdk/rep... ). Plus, our open-source nature means
45.
▲
by
vadman97
3y ago
The open-source infra we use allows us to have a highly-available, scale-able system. Kafka - buffers data ingest so that we never lose recordings. Redis - acts as a cache, optimized for write-heavy processing in our app. Postgres - stores
46.
▲
by
vadman97
3y ago
For the cloud version (app.highlight.io), we currently don't support plugging into your own infrastructure. We also don't give you direct access to the database we use. For the self-hosted version however, you can use any infrastr
47.
▲
by
vadman97
3y ago
Yes, our self-hosted option can plug into existing ClickHouse servers and will set up the necessary schema for highlight to function. The infrastructure configuration is driven by the docker compose file. More info in our docs: https:/
48.
▲
by
vadman97
3y ago
That's one way to summarize it :) We do quite a bit more though with session replay and error monitoring for your full-stack web apps.
49.
▲
by
vadman97
3y ago
Haven't heard of it unfortunately. What kind of time series data are you thinking of storing? If you're building an application on top of it, you're better off using an OLAP DB like ClickHouse, InfluxDB, etc. to have access t
50.
▲
by
vadman97
3y ago
Interesting, thanks for sharing. Do you implement your own storage with Quickwit or can it be backed by a cloud storage solution like S3? Our session replay is similar to OpenReplay but we've focused a lot of effort on making a cohesiv
51.
▲
by
vadman97
3y ago
What does you ingest setup look like with BigQuery? Are you using something like fluentd to pipe logs over?
52.
▲
by
vadman97
3y ago
You get structured attribute search without a schema with Highlight. More in our docs: https://www.highlight.io/docs/general/product-features/loggi...
53.
▲
by
vadman97
3y ago
Highlight is a full-stack observability platform, so our recordings start from a user's frontend session and associate server-side errors and logs to provide debugging context. We've been building quite a lot to bolster the backen
54.
▲
by
vadman97
3y ago
The new feature we're announcing is the server-side + browser-side logs ingest, query interface, and alerting engine. Our web session recording product is something we've had around but now closely integrates with logs to help you
55.
▲
by
vadman97
3y ago
We have had folks in our Discord successfully run highlight on a Raspberry Pi with 4GB RAM, so our recommendation is definitely on the safe side. We're running multiple infra services in the docker stack (postgres, opensearch, clickhou
56.
▲
by
vadman97
3y ago
Apologies for the inconsistency here. Our Docker resource requirement recommendations were out of date after some recent improvements ( https://github.com/highlight/highlight/pull/5074 and https://g
57.
▲
by
vadman97
3y ago
For us, a significant reason was the ClickHouse cloud-hosted offering, rather than having to manage a cluster ourselves. Their use of S3 as the backing storage medium means that large-scale data retention is quite affordable. A good compari
58.
▲
by
vadman97
3y ago
Apologies for the confusion. We meant to link to our main readme: https://github.com/highlight/highlight/blob/main/README.md
59.
▲
Show HN: We built a ClickHouse-based logging service
(github.com)
192 points
by
vadman97
3y ago
|
110 comments
60.
▲
by
vadman97
4y ago
highlight.io: https://github.com/highlight#our-values
More ›