Observability Backend Not Found

URI: https://docs.ankatech.co/errors/observability-backend-not-found
HTTP Status: 404 Not Found

When you see this

No observability backend matches the identifier in the request path. On the platform plane a backend is addressed by its id; on the tenant planes a destination is addressed by its name within that tenant. The body names neither the identifier nor anything about the deployment's configuration.

Common Causes

• The backend or destination was deleted, or never existed.
• The id or name in the path is mistyped.
• Addressing a tenant destination by name under a different tenant than the one that owns it.

Response Example

{
  "type": "https://docs.ankatech.co/errors/observability-backend-not-found",
  "title": "Not Found",
  "status": 404,
  "detail": "Observability backend not found.",
  "instance": "/api/v3/admin/platform/observability/backends/7c9e6679-7425-40de-944b-e07fc1f90ae7"
}

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

How to Resolve

1. List the observability backends in the scope you are addressing and confirm the identifier.
2. On the tenant planes, confirm you are addressing the destination under the tenant that owns it.
3. If the backend was deleted, create it again rather than retrying the update.

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