Observability Signal Not Permitted

URI: https://docs.ankatech.co/errors/observability-signal-not-permitted
HTTP Status: 400 Bad Request

When you see this

A tenant observability destination was saved subscribed to LOGS. Nothing was saved and nothing was rendered. Only platform observability backends export logs: a platform log line can carry other tenants' identifiers in its text, so it cannot be filtered down to one tenant. A tenant destination may subscribe to TRACES and METRICS.

The refusal applies whoever writes the destination: the tenant administrator, or a platform administrator provisioning it on the tenant's behalf. It does not depend on the release state.

Response Example

{
  "type": "https://docs.ankatech.co/errors/observability-signal-not-permitted",
  "title": "Observability Signal Not Permitted",
  "status": 400,
  "detail": "signals: LOGS is exported only by platform observability backends; a tenant observability destination may subscribe to TRACES and METRICS.",
  "instance": "/api/v3/admin/tenants/550e8400-e29b-41d4-a716-446655440000/observability-backends",
  "timestamp": 1790000000,
  "extensions": {
    "requestId": "7b2e4d90-1c3f-4a68-9e5b-0d8f6a2c7e14"
  }
}

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

How to Resolve

1. Remove LOGS from signals and save again.

Operations that emit it

Related Errors

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