3 ms·
This is such a well-executed idea, Ali, the "context loss" problem during incident response is very real and painful. Love how RobinRelay bridges historical dis
by gujjar19 1y ago
This is such a well-executed idea, Ali, the "context loss" problem during incident response is very real and painful. Love how RobinRelay bridges historical discussions across teams within Slack itself — no new dashboards to log into, and no brittle integrations needed.
A few things I’d love to hear more about:
How does RobinRelay handle conflicting advice or noisy past threads?
Can it differentiate between alert variants (e.g., same service but different error codes)?
Any future plans to surface trends like “this alert usually precedes X outage”?
For teams drowning in alerts and Slack chaos, this looks like game changer
- alibasharat5 1y agoThank you so much really appreciate the kind words... You are right.Context loss during incident response is the problem we’re aiming to solve deeply, especially for teams that live in Slack and don’t want to chase dashboards. Let me try to answer your great questions: 1. Conflicting advice or noisy threads: Right now, RobinRelay summarizes past replies per alert occurrence (thread), then aggregates them across all past occurrences of the same (e.g., “CPU spike on api-server”). If conflicting advice exists (e.g., restart vs scale up), we preserve each cause separately and display them like: “In the past, this alert was caused by: – autoscaler OOM restart (3x) – DB connection saturation (2x)” We’re working on tagging which ones were “confirmed fixes” vs just investigative noise and will open that to user feedback soon. Alert variants: We normalize alerts our algorithm similar to finger prints for vector db. We’re exploring multiple ways like fuzzy hashing, LLM's, custom way to detect meaningful variants (e.g., same service, different root cause) and eventually flag them as “related but distinct”. Trend detection (e.g. precursor alerts): Yes! This is on our roadmap. We want to show timelines like: If you're seeing these pain points first-hand, I’d love to chat or hear how your team handles it today — this kind of feedback shapes the product every week. Thanks again for the thoughtful comment