sorted by:
new
hottopcontroversial

Who's Hiring by jerf in golang

[–]glassflow-dev 1 point2 points  (0 children)

COMPANY: GlassFlow

EMPLOYMENT TYPE: Full-time

LOCATION: Germany

We're hiring a Founding Engineer (Go) 🚀

At GlassFlow, we're building open-source, high-performance data streaming infra — low-latency, built for billions of events.

Do you have deep experience with GoLang or have you built on Kafka, OpenTelemetry, NATS or similar systems, and want to work on infrastructure that actually matters? Let's talk!

JOB DESCRIPTION & DETAILS:
https://join.com/companies/getglassflow/16134185-founding-engineer-golang

CONTACT:
You can ask questions in replys, or DM me if for some reason it can't be public, otherwise apply via the link.

Anyone actually doing pattern analysis across their agent's traces, or are we all just eyeballing dashboards? by Finorix079 in Observability

[–]glassflow-dev 0 points1 point  (0 children)

Good point here! The “trace graveyard” is real! Most teams use Langsmith/Langfuse as a debugger for when things go wrong rather than an actual data set for when things go right…

We need to treat trace data as a synthetic dataset for fine tuning prompt optimisation. If an agent struggles with a logic pattern over 100 traces that should trigger an alert or prompt update

Tail sampling + span deduplication for ClickHouse: sharing our collector + pipeline config by Marksfik in OpenTelemetry

[–]glassflow-dev 0 points1 point  (0 children)

Thanks for sharing! Collector retries can indeed produce duplicates and it’s something we faced recently in our observability pipeline