Entries
Entries are telemetry records stored in Casdoor. Each entry holds a payload (OTLP traces, metrics, logs, OS log records, or permission audit events) along with metadata about who sent it.
Entry properties
| Field | Description |
|---|---|
| Name | Unique identifier for the entry within the organization |
| Display name | Human-readable label |
| Provider | The Log provider that created this entry |
| Type | trace, metrics, log, permission, or system depending on the source |
| Client IP | IP address of the sender (for OTLP entries received over HTTP) |
| User agent | HTTP User-Agent of the sender (for OTLP entries received over HTTP) |
| Application | The Casdoor application this entry is associated with |
OpenTelemetry data (OTLP)
Casdoor accepts all three OTLP signal types pushed by an OpenClaw agent:
| Endpoint | Type stored | Entry type |
|---|---|---|
POST /api/v1/traces | Traces | trace |
POST /api/v1/metrics | Metrics | metrics |
POST /api/v1/logs | Logs | log |
All three endpoints require Content-Type: application/x-protobuf. The OTLP protobuf payload is serialized to JSON and stored in the Message field. The entry's ClientIp and UserAgent fields are populated from the HTTP request.
Access control: The sender's IP must match the Host field of an Agent/OpenClaw Log provider in the same organization. Requests from unrecognized IPs are rejected with 403 Forbidden. Leave Host empty to allow any IP.
On the entry edit page, the EntryMessageViewer renders trace-type entries as a structured span tree with timing, attributes, and status.
Permission audit logs
When a Casdoor Permission Log provider is configured for an organization, Casdoor writes one entry per non-GET API call, recording the subject, method, URL, and whether the request was allowed or denied. These entries have Type: permission and are linked to the provider that created them via the Provider field.
Managing entries
Navigate to Entries in the Casdoor sidebar. Each entry is scoped to an organization. Entries generated by providers are created automatically and are read-only.
Permission audit logs
When a Casdoor Permission Log provider is configured for an organization, Casdoor writes one entry per non-GET API call, recording the subject, method, URL, and whether the request was allowed or denied. These entries have Type: permission and are linked to the provider that created them via the Provider field.
Managing entries
Navigate to Entries in the Casdoor sidebar. Each entry is scoped to an organization. Entries generated by providers are created automatically and are read-only.