Uploaded October 2026 | Updated November 2026, 3 days ago
Investigate application incidents with an SRE Copilot that uses natural-language questions, read-only MCP tools, and log evidence from an observability pipeline. See native Log Analytics and LoganAI alongside a custom incident portal that helps reliability engineers identify error patterns, compare time windows, and review evidence before deciding next steps.
Chapters:
0:00 SRE incident copilot architecture
4:30 Investigate logs with native Log Analytics and LoganAI
7:14 Use the custom incident copilot portal
11:05 Adapt the solution to your telemetry
The architecture ingests synthetic application logs from a VM through OCI Logging, Service Connector Hub, parsers, and Log Analytics. A FastAPI application and Model Context Protocol (MCP) server run privately on Kubernetes and provide three bounded, read-only tools: search incident events, retrieve error timelines, and identify top error patterns and related deployment versions.
Use this pattern when SREs or platform teams need an extensible portal for incident investigation outside the console. The walkthrough examines configuration mismatches, deployment regression in version 1.2, and downstream timeouts. Copilot responses return evidence, hypotheses, confidence signals, and suggested manual validation steps; they do not perform automated remediation.
Additional information:
This demonstration uses synthetic application logs. The Kubernetes application is accessed through private port-forwarding; public SSO access is not demonstrated.
Key links:
Oracle Log Analytics documentation: docs.oracle.com/en-us/iaas/log-analytics/home.htm
Oracle Kubernetes Engine documentation: docs.oracle.com/en-us/iaas/Content/ContEng/home.htm
OCI Generative AI documentation: docs.oracle.com/en-us/iaas/Content/generative-ai/home.htm
Explore more Code Innovate videos:
youtube.com/playlist?list=PLPIzp-E1msrZMCfSHbKgLK3KWsNM9JB9a
#codeinnovate #SRE #IncidentResponse #MCP #LogAnalytics
Investigate application incidents with an SRE Copilot that uses natural-language questions, read-only MCP tools, and log evidence from an observability pipeline. See native Log Analytics and LoganAI alongside a custom incident portal that helps reliability engineers identify error patterns, compare time windows, and review evidence before deciding next steps.
Chapters:
0:00 SRE incident copilot architecture
4:30 Investigate logs with native Log Analytics and LoganAI
7:14 Use the custom incident copilot portal
11:05 Adapt the solution to your telemetry
The architecture ingests synthetic application logs from a VM through OCI Logging, Service Connector Hub, parsers, and Log Analytics. A FastAPI application and Model Context Protocol (MCP) server run privately on Kubernetes and provide three bounded, read-only tools: search incident events, retrieve error timelines, and identify top error patterns and related deployment versions.
Use this pattern when SREs or platform teams need an extensible portal for incident investigation outside the console. The walkthrough examines configuration mismatches, deployment regression in version 1.2, and downstream timeouts. Copilot responses return evidence, hypotheses, confidence signals, and suggested manual validation steps; they do not perform automated remediation.
Additional information:
This demonstration uses synthetic application logs. The Kubernetes application is accessed through private port-forwarding; public SSO access is not demonstrated.
Key links:
Oracle Log Analytics documentation: docs.oracle.com/en-us/iaas/log-analytics/home.htm
Oracle Kubernetes Engine documentation: docs.oracle.com/en-us/iaas/Content/ContEng/home.htm
OCI Generative AI documentation: docs.oracle.com/en-us/iaas/Content/generative-ai/home.htm
Explore more Code Innovate videos:
youtube.com/playlist?list=PLPIzp-E1msrZMCfSHbKgLK3KWsNM9JB9a
#codeinnovate #SRE #IncidentResponse #MCP #LogAnalytics










