code0Vörr AIContactGuides
Book a Demo
Guides/Shankh/Operate

Configure AI analysis

Cloud IntegrationIntermediate4 min

AI incident analysis is not implemented in Shankh. There is no provider picker, key field, model choice or Frigga-provided key anywhere in the product, and the AI summary and AI postmortem in Reports are text templates assembled from the incident record — no model is called. This guide records the intended shape of the feature; it is not something you can configure today.

AdminAI-analysis configuration requires Admin access.

Add a provider key

  1. Open Cloud Integration and go to the AI-analysis configuration.
  2. Choose the provider — Anthropic or OpenAI.
  3. Paste the API key into the key field.
  4. Save the configuration.
  5. Confirm it shows as active.
None of these controls exist in the product yet. Do not send this section to customers as instructions.

The intent is that keys are stored encrypted, that a customer key takes priority over a Frigga-provided one, and that a Frigga-provided key covers one free use.

Rotate or remove the key

  1. Open the AI-analysis configuration.
  2. Replace the key with the new one, or clear it to disable AI analysis.
  3. Save the configuration.
  4. Confirm a new incident shows analysis from the new key, or none if you removed it.
Nothing is stored today, so there is no key to rotate and no past analysis to retain on old incidents.

If analysis does not appear

Analysis never appears today, because the feature does not run. If it ships, these are the causes worth checking first:

  • No customer key and no available Frigga-provided use is configured.
  • The saved key is invalid, revoked or out of quota at the provider.
  • The incident predates the configuration being saved.
Nothing here is diagnosable in the current product — an incident with no AI analysis is behaving normally.

Acknowledgement, escalation, notification, status updates and resolution do not depend on AI analysis being enabled.