mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-08-28 05:25:33 +00:00
434c86e2c3
Keep docs asset URLs repo-root-relative and pass images as literal MDX children so Mintlify can compile them through OptimizedImage under the /docs mount. Mintlify's official guidance says: “Image paths are root-relative from your docs repository.” It also says relative paths such as `./screenshot.png` are unsupported. See [Image embeds](https://www.mintlify.com/docs/create/image-embeds). The existing `/images/...` paths were correct. The failure came from passing them through custom-component string props, which kept Mintlify from seeing those images during its MDX transform. - fix hero, building-block, and Slack avatar images - preserve Slack avatar clipping - normalize Hermes and Company Brain icon sizing Tested with Mintlify validation, broken-link checks, and browser checks across every changed route.
48 lines
2.3 KiB
Text
48 lines
2.3 KiB
Text
---
|
|
title: "Incidents & Downtime Chatter"
|
|
sidebarTitle: "Incidents"
|
|
description: "Answer 'is prod down?' from live Sentry, and post scheduled error digests"
|
|
icon: "triangle-alert"
|
|
---
|
|
|
|
import { SlackThread, SlackMessage, AgentLink } from "/snippets/slack-message.mdx";
|
|
|
|
## The scenario
|
|
|
|
Someone drops a vague "is prod down?" in `#eng`. Company Brain correlates it with what's actually failing right now — and a separate automation keeps a daily error digest flowing without anyone asking.
|
|
|
|
## What happens
|
|
|
|
<SlackThread channel="#eng" members={48}>
|
|
<SlackMessage name="Alex" color="#E01E5A" time="11:03 AM">
|
|
is prod down? a couple of customers are pinging me
|
|
</SlackMessage>
|
|
<SlackMessage bot hasAvatar time="11:03 AM">
|
|
<img src="/images/company-brain/supermemory-slack-icon.png" alt="" />
|
|
Not a full outage — **`api/search` is elevated** (42 errors in the last 15m, mostly `timeout on vectorize`). Sentry issue <AgentLink href="https://example.com">SM-2041</AgentLink>. Deploy from this morning is the likely culprit; rollback candidate is `af61880`.
|
|
</SlackMessage>
|
|
</SlackThread>
|
|
|
|
Or, without anyone asking, a scheduled automation posts every morning:
|
|
|
|
<SlackThread channel="#eng">
|
|
<SlackMessage bot hasAvatar time="9:00 AM">
|
|
<img src="/images/company-brain/supermemory-slack-icon.png" alt="" />
|
|
**Daily error digest** — 3 issues new since yesterday, 1 still spiking (`api/search` timeout). Full list in Sentry.
|
|
</SlackMessage>
|
|
</SlackThread>
|
|
|
|
## What's really going on
|
|
|
|
The first exchange is a [chime-in](/company-brain/automations) (or an @mention — either works) that hits the **Sentry** [tool connector](/company-brain/connectors) for live error data. The second is an [automation](/company-brain/automations): a recurring prompt on a cron that posts to a channel using org-shared connections only, so it never runs as a specific person.
|
|
|
|
If the channel is private, only an admin can target it with an automation, and the bot fails closed if it can't verify visibility.
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Connectors" icon="plug" href="/company-brain/connectors">
|
|
Connect Sentry (and friends) for live incident context.
|
|
</Card>
|
|
<Card title="Automations" icon="wand-magic-sparkles" href="/company-brain/automations">
|
|
Schedule digests and understand chime-in.
|
|
</Card>
|
|
</CardGroup>
|