This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Tayga
Turn OpenTelemetry traces into root-cause error stories
Tayga turns OpenTelemetry traces and logs into error stories. For each failing or slow request it shows the root-cause span, the path across services, the critical path, what differs from normal, and the related logs.
Hi everyone, I'm Krzysztof, and I built Tayga.
When a request fails in a traced system, you usually have to find the trace, open the waterfall and work out which span actually broke. Tayga does that work while the traces stream in. For every failing or slow request it builds an error story:
• the root-cause span, described in a sentence like "checkout could not reach payment"
• the request path across services, and the critical path
• a diff against the endpoint's normal behaviour over the last hour: operations that are new, missing or slower
• the logs that matter
When the same problem repeats, it folds into one story group with a trend, so you don't get hundreds of separate traces. Tayga also mines your logs into templates as they arrive and alerts on new, spiking or silent ones, sending them to a webhook or Slack.
A few deliberate choices:
• No LLM in the root cause. It uses fixed rules over the span tree, so the same input always gives the same answer.
• Standard OTLP in. Any OpenTelemetry Collector connects with one exporter, and Tayga can run alongside Jaeger, Grafana or whatever you already use.
• Self-hosted, AGPLv3, written in Rust, with ClickHouse for storage and Redpanda for streaming.
Watch the 3½-minute tour: https://softberries.github.io/ta...
The name comes from my hunting dog, Tajga, who can trace anything, anywhere.
I'd like feedback, especially from people running OpenTelemetry in production: what would you need to see before you trusted a root cause from a tool like this?
About Tayga on Product Hunt
“Turn OpenTelemetry traces into root-cause error stories”
Tayga was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #157 on the daily leaderboard. Tayga turns OpenTelemetry traces and logs into error stories. For each failing or slow request it shows the root-cause span, the path across services, the critical path, what differs from normal, and the related logs.
On the analytics side, Tayga competes within Open Source, Developer Tools and GitHub — topics that collectively have 631.9k followers on Product Hunt. The dashboard above tracks how Tayga performed against the three products that launched closest to it on the same day.
Who hunted Tayga?
Tayga was hunted by Krzysztof Grajek. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Tayga including community comment highlights and product details, visit the product overview.
Krzysztof Grajek