The Context Lake: what Noci AI reads
The Context Lake is where Noci AI keeps what an incident needs. It reads GitHub pull requests and deploys, AWS change events, alerts from your monitoring tools, past incidents and their postmortem drafts, the Slack conversations Noci is part of, and support tickets during an incident. Agents recall similar past incidents.
What does Noci AI read?
At the start of an incident the facts are scattered: the alert in a monitoring tool, the deploy in a pipeline, the complaint in a ticket queue, the discussion in chat. The Context Lake brings them to one place, tied to the service they concern, so people and agents start from the same facts.
| What | Where it comes from | Why an incident needs it |
|---|---|---|
| Pull requests and deploys | GitHub | What changed shortly before the alert |
| Cloud changes | AWS CloudTrail and change events | What moved in the infrastructure |
| Alerts | Datadog, New Relic, Coralogix, Amazon CloudWatch | What fired, when, and how often before |
| Incident history and postmortem drafts | Noci AI itself | What happened last time |
| Conversations | The Slack conversations Noci is part of | What people already tried and said |
| Support tickets | Zendesk, Freshdesk, Intercom | Whether customers are already reporting it |
Support tickets are read while an incident is open. The integrations page lists every tool Noci AI connects to.
How do agents use it?
Agents investigate with this context and write what they found back to the same place, so the next person starts from it. When they investigate, agents recall similar past incidents.
AI SRE describes what the investigation produces, and incident response in Slack shows where the findings land.
What is not there yet?
Customer impact from billing and CRM is not available yet: Customer impact from billing and CRM Coming.
For the plain-language definition, see what an incident context lake is.
Questions
What does the Context Lake read?
GitHub pull requests and deploys, AWS CloudTrail and change events, alerts from Datadog, New Relic, Coralogix and Amazon CloudWatch, incident history and postmortem drafts, the Slack conversations Noci is part of, and support tickets from Zendesk, Freshdesk and Intercom during an incident.
Is it the same as a data lake?
No. A data lake keeps data to analyze later. The Context Lake is organized around an incident, so the alert, the change, the ticket and the conversation are read together.
Does the Context Lake use credits?
The Context Lake, Noci's map of your services, is included and never uses credits.