Skip to main content

Predefined datasets

Predefined datasets live in the default dataspace, next to the datasets you create. Coralogix defines each one's schema and entity type, but your own data fills it: the RUM events your SDK sends, the event markers you post, the AI telemetry your applications emit.

In Dataset Management, the Managed by column shows Predefined for these datasets. You can't delete or rename a predefined dataset or change its write access, but you can set its quota limit and access policy. Predefined datasets don't count toward your dataset limit. See Dataset management.

Queryable datasets​

DatasetEntity typeDescription
ai.evaluationsaiEvaluationsGenAI evaluation results, including user feedback scores.
ai.sessions.claudeaiSessionsClaudeClaude Code session content: prompts, responses, tool calls, and errors.
ops.eventsopsEventsEvent markers, such as deployments, sent through the ops-events API.
rum.eventsbrowserLogs/v2Real User Monitoring events from your browser SDK.

Query a predefined dataset by name, with or without the default/ prefix:

source default/ops.events

Every predefined dataset in this table carries the standard log record envelope: engine metadata in $m, labels in $l, and the dataset-specific payload in $d. See Entity types for how the envelope works.

Storage datasets​

Some predefined datasets hold files that power Coralogix features rather than records you query. They appear in Dataset Management so you can see them and set their quota limit and access policy. Their entity types belong to the binary pillar, which stores files but doesn't structurally query them.

DatasetWhat it stores
sessionRecordingsRUM session recordings.
sessionSnapshotsSession snapshot data.
mobileSnapshotsMobile application snapshots.
sourceMapsWeb application source maps.
dsymiOS debug information (dSYM files).
proguardAndroid debug information (ProGuard mapping files).

Next steps​

Last updated on
Was this page helpful?