Skip to main content
An event log entry is generated by Control Plane, or by a platform component acting on your behalf (a Managed Kubernetes autoscaler reporting a failed scaling activity, for example); you do not create them directly. Most resource kinds expose a /-eventlog subresource that lists the events recorded against that one resource, newest first.

Example

Fields

Context

context also accepts additional fields specific to the component that recorded the event.

Deduplication

An event with a context.fingerprint is deduplicated against events already recorded for the same resource: at most one entry per fingerprint is recorded within a 24-hour window. A repeat within that window does not create a new entry; instead it increments the existing entry’s eventCount and updates its lastEventTime. The recording component chooses the fingerprint, and many components include a time bucket in it (for example, one hour), so a recurring condition can produce a new entry more often than once a day. Setting pinned: true exempts an event from this deduplication, so every occurrence is recorded as its own entry. Events with no fingerprint are never deduplicated.

Permissions

Viewing a resource’s event log requires view on that resource. There is no separate eventlog permission, and event log entries are not something you create directly — see the permission model for the permissions on the resource itself.

Supported Resources

The following kinds expose /-eventlog: agent, audit context, cloud account, domain, group, GVC, identity, IP set, Managed Kubernetes cluster, org, policy, secret, service account, user, volume set, and workload.

CLI

This is unrelated to tailing container output, which is the separate cpln logs command with LogQL syntax. --max (default 50) caps how many entries are returned; a value less than 1 returns all entries. eventlog is documented on the CLI reference page for each supporting kind: agent, audit context, cloud account, domain, group, GVC, identity, IP set, mk8s cluster, org, policy, secret, service account, user, volume set, and workload.

API

The response is a standard paginated list, sorted newest first, with a target link back to the resource the events belong to.