<!-- Generated from the canonical HTML page. Do not edit separately. -->
# Investigate production incidents - Ankra Use Cases

Canonical: https://ankra.ai/use-cases/incident-response

Give your team and its agents the logs, events and resource state needed to investigate a running application.

[All use cases](https://ankra.ai/use-cases)

Investigate production incidents

# From an unhealthy service to an informed next step.

Give your team and its agents the logs, events and resource state needed to investigate a running application.

[Start with Ankra](https://platform.ankra.app/auth/signup)  [Read the guide](https://docs.ankra.ai/platform/kubernetes-ai-troubleshooting)

For developers, sres and teams on call

The work to take off your team

## The hardest part of a failure is often gathering enough context to understand it.

Ankra brings workload state, recent operations, logs and metrics into the same environment. Agents can use that evidence to explain likely causes and propose a change through the tools and permissions you allow.

With Ankra

### An investigation grounded in the system that is actually running.

Find the affected workload  Gather the evidence  Ask for a proposed fix  Verify recovery

A practical path

## How this works with Ankra.

1. 01

  ### Find the affected workload

  Start with the deployment, alert or failed operation and its current state.
2. 02

  ### Gather the evidence

  Inspect pod logs, events, resource relationships and relevant metrics.
3. 03

  ### Ask for a proposed fix

  Let an agent investigate with scoped tools and explain the evidence behind its recommendation.
4. 04

  ### Verify recovery

  Review gated actions, follow the operation and check the application after the change.

 [Follow the product guide](https://docs.ankra.ai/platform/kubernetes-ai-troubleshooting)

The platform behind the workflow

## The pieces, already connected.

[### Live troubleshooting Investigate a failed build, crash loop or unhealthy service using its logs, events, manifests and resource state.](https://ankra.ai/features#diagnostics)

[### Metrics, logs & health Understand the application and the cluster underneath it, with resource views, metrics and logging integrations.](https://ankra.ai/features#observability)

[### Alerts & notification routing Send the right platform events to the right team, filtered by cluster, severity and notification kind.](https://ankra.ai/features#alerts)

What comes next?

## Keep building from here.

[Operate & protect ### An AI platform engineer Agents that read live cluster state, fix what breaks and wait for your approval. Use Ankra's AI team, or connect Claude, Cursor or your own agent over MCP.](https://ankra.ai/use-cases/ai-platform-engineer)

[Operate & protect ### Self-service with control Give developers and agents useful access while retaining ownership of permissions, configuration and changes.](https://ankra.ai/use-cases/team-governance)

[Build & ship ### Application delivery & CI/CD Bring testing, builds, security scans, images and deployment into one delivery workflow.](https://ankra.ai/use-cases/ci-cd-pipelines)

Your next chapter

## You built it.
*Let’s get it live.*

Give your application a path to production.
 Give your team a simpler way to run it.

[Get your app live](https://platform.ankra.app/auth/signup)  [Try a playground](https://ankra.ai/playground)

First 30 vCPU of platform usage included.
Try it without a card; a card unlocks full access and €59 of credit.

From something you built
to something people use.

- Deploy from your repository
- Run on infrastructure you choose
- Operate with your team and agents