Proactive Incident Intelligence: Syncing Checkly Monitoring into Cognee Memory with dlt

Description and use

Synchronizing Checkly metadata into Cognee via dlt enables AI agents to quickly obtain context on failures, alert channels, and maintenance windows.

Problem

Engineering teams need contextual information about synthetic monitoring failures, alert channels, and maintenance windows during incidents.

Outcome

The connector synchronizes Checkly metadata into Cognee, preserving secret‑safe headers and environment variables, propagating health status, and handling deletions via tombstones, enabling AI agents to answer incident‑related questions.

Workflow

• Install cognee and cognee-community-connector-checkly via pip
• Set CHECKLY_API_KEY (and optional CHECKLY_ACCOUNT_ID) as environment variables
• Create a checkly_source with desired resources
• Call cognee.remember with merge write disposition to ingest data
• Query Cognee memory with a graph completion search for incident context

Evidence

The connector follows a key‑only redaction strategy for supported headers and environment variables.

Source

The connector is designed to retrieve check‑status information through the /v1/check-statuses endpoint and associate the results with relevant monitoring records.

Source

It also uses a _deleted tombstone mechanism with hard‑delete semantics to represent upstream deletions.

Source