cd /news/ai-agents/building-outage-memory-for-ai-agents… · home › topics › ai-agents › article
[ARTICLE · art-156182] src=dev.to ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Building Outage Memory for AI Agents: Better Stack Connector for Cognee

A developer contributed a Better Stack connector to the cognee-community repository that pulls incident data from Better Stack's REST API v2 and ingests it into Cognee as structured markdown documents, so AI agents can query outage history through a knowledge graph. The connector handles pagination and exponential backoff retries on HTTP 429/5xx responses, and tags documents with cognee_document_source = "better_stack" so Cognee links endpoints, error codes and resolution steps for later recall.

by read1 min views3 publishedOct 23, 2026

High availability is the bedrock of any software system. Monitoring tools like Better Stack (Better Uptime) track endpoint heartbeats, SSL validity, API responsiveness, and on-call paging around the clock.

Yet, when incidents happen, the knowledge is often trapped in incident dashboards and alert history logs.

By integrating Better Stack with Cognee, we can transform infrastructure telemetry and outage reports into queryable knowledge graphs for AI engineering agents.

Autonomous AI coding agents, DevOps assistants, and support bots frequently need infrastructure context:

With the better_stack connector for Cognee, this telemetry becomes part of the AI's long-term memory.

The connector lives in packages/connector/better_stack/ within cognee-community.

The connector calls Better Stack's REST API v2 (/incidents and /incidents/{id}/timeline), handling pagination and exponential retry backoff on HTTP 429/5xx responses.

Each outage report is structured into markdown format for Cognee's entity extraction:


- **Status:** resolved
- **Started At:** 2026-10-12T08:00:00Z
- **Resolved At:** 2026-10-12T08:14:00Z

## Root Cause & Description
Upstream backend timed out during deployment rollback.

## Chronological Timeline
- **[2026-10-12T08:00:00Z]** Triggered - Monitor check failed 3 consecutive times
- **[2026-10-12T08:02:00Z]** Acknowledged - Engineer on-call acknowledged via Slack
- **[2026-10-12T08:14:00Z]** Resolved - Rollback completed and healthy probes returned HTTP 200

Because the source specifies cognee_document_source = "better_stack", Cognee treats each outage report as a first-class knowledge document. The graph links endpoints, error codes, and resolution steps so agents can recall operational history instantly.

import asyncio
import cognee
from cognee_community_connector_better_stack import better_stack_source

async def main():
    source = better_stack_source()
    await cognee.add(source)
    await cognee.cognify()

    results = await cognee.search("Which services experienced downtime last week?")
    for res in results:
        print(res)

if __name__ == "__main__":
    asyncio.run(main())

Operational observability meets AI memory—ensuring your agents never forget past system lessons.

── more in #ai-agents 4 stories · sorted by recency
── more on @cognee 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/building-outage-memo…] indexed:0 read:1min 2026-10-23 · —