Skip to content

Observability Backend Duplicate Name

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

When you see this

The name you submitted is already taken by another observability backend in the same scope. Names are unique per deployment for the platform backends, and unique per tenant for a tenant's own destinations. The same problem type is also returned when a concurrent create races the pre-check and hits the unique-name database constraint.

Common Causes

  • Creating a backend with a name that already exists in the same scope.
  • Renaming a backend to a name another backend in the same scope already holds.
  • Two concurrent creates submitting the same name, where the second reaches the unique constraint.

Response Example

{
  "type": "https://docs.ankatech.co/errors/observability-backend-duplicate-name",
  "title": "Conflict",
  "status": 409,
  "detail": "An observability backend with that name already exists.",
  "instance": "/api/v3/admin/platform/observability/backends"
}

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

How to Resolve

  1. List the existing observability backends in this scope and pick a name that is not in use.
  2. If you intended to change an existing backend, update that backend rather than creating a second one under a variant name.
  3. If two operators created the same name at once, re-read the list — the other create succeeded.

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