Skip to main content

Search Logs

What you get​

Logs in Custd are ordinary events. Any event whose payload or context carries a severity, service, sub-client or resource gets those values stored as indexed columns, so Logs (/logs) can filter one UTC day by them and show each line's message. There is no separate log pipeline, schema type or agent.

Send log lines​

Send log lines like any other event: register an event schema for them, then send events with a released SDK or the API. Name the fields so Custd can find them. The first match wins, and the payload is checked before the context:

FilterPayload fieldsContext fields
Severityseverity, level, logLevelseverity, level, log.level
Serviceservice, serviceName, app, appName, program, loggerservice, serviceName, app, appName, logger
Sub-clientsubClient, sub_client, subClientId, clientId, clientthe same names
Resourceresource, host, hostname, server, instancethe same names

Put the human-readable line in message, msg or body; the explorer shows its first line.

{
"eventTypeSlug": "app-log",
"schemaVersion": "1.0.0",
"timestamp": "2026-11-13T09:30:00.000Z",
"payload": {
"severity": "error",
"service": "checkout",
"host": "web-2",
"message": "Payment provider timed out after 30s"
}
}

The fields keep their original place in the stored event, so nothing is lost by naming them this way.

  1. Open Logs (/logs) and choose the Date (one UTC day).
  2. Optionally narrow by Event type, Severity, Service, Sub-client or Resource. Each is an exact match. Severity suggests the common levels, but any value your producer sends works.
  3. Set Limit (1 to 1,000 rows) and select Search.
  4. Read Coverage before the rows. Incomplete coverage means part of the day is not prepared yet, so the rows are partial; see Ready data.
  5. Use the row search to narrow the returned rows, and open a row to see the whole event.

The address bar keeps your filters, so you can share or bookmark a search.

The same filters work on the query API: add severity, service, subClient or resource to a POST /api/v1/analytics/query or query-range body. See Query analytics.

Limits​

  • A search covers one UTC day. Use the query API's range route for several days.
  • Filters are exact matches; for a phrase in the message, use the row search on the returned rows.
  • Application errors with stack traces belong in Track errors, which groups them into issues and alerts you.