Skip to content

Observability Backend Cap Exceeded

URI: https://docs.ankatech.co/errors/observability-backend-cap-exceeded
HTTP Status: 409 Conflict

When you see this

A create was refused because the soft cap on simultaneously-configured observability backends has been reached. The cap is five, enforced before anything is sealed or persisted. It applies both to the deployment-wide platform backends and, separately, to each tenant's own set of observability destinations.

Common Causes

  • Creating a sixth deployment observability backend when five already exist.
  • Creating a sixth observability destination for a tenant that already has five.

Response Example

{
  "type": "https://docs.ankatech.co/errors/observability-backend-cap-exceeded",
  "title": "Conflict",
  "status": 409,
  "detail": "The maximum number of observability backends has been reached.",
  "instance": "/api/v3/admin/platform/observability/backends"
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Delete an observability backend you no longer export to, then create the new one.
  2. If an existing backend is simply pointing at the wrong destination, update it in place instead of creating another.
  3. Consolidate signals onto fewer backends where the same collector can receive them.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.