actedUpon | string (uuid) | Yes | ID of the entity on which the event was performed. |
action | string | Yes | Action taken on the resource, for example import. |
category | string | Yes | Resource kind the operation was invoked on, for example pattern. |
createdAt | string (date-time) | Yes | Timestamp when the event was recorded. |
deletedAt | string | null (date-time) | No | Timestamp when the event was soft-deleted; omitted when it was not. |
description | string | Yes | Human-readable summary of what happened. |
id | string (uuid) | Yes | Event ID. |
metadata | object | null | Yes | Event-specific details; the structure varies by event kind. null when the producer attached none. It stays a free-form map; design events fill it with a named shape: RelationshipEvaluationEventMetadata (category relationship, action evaluation), DesignValidationEventMetadata (category pattern, actions validate, deploy, undeploy, dry-run) and DesignSavedEventMetadata (category pattern, actions create, update); ScheduleCompletedEventMetadata (category schedule, action completed); DesignEventIdentity names the design. Never put design contents into event metadata - no designFile, patternFile, components, relationships, trace, evaluationResponse, the raw summary or validationResult. Meshery Server applies a 16 KB guard that drops oversized metadata down to the identity fields (designId, designName, designVersion, designLink, viewLink). On an error event, metadata.error holds only the MeshKit error, never the design or the request that failed; a design validation event whose operation did not complete (status error) carries it as a DesignEventOperationError. Older Meshery Cloud rows may carry the legacy design_name and view_link keys; readers should fall back to them when designName and viewLink are absent. |
operationId | string (uuid) | Yes | ID correlating the events one operation emitted. |
owner | string (uuid) | No | A Universally Unique Identifier used to uniquely identify entities in Meshery. The UUID core definition is used across different schemas. |
organizationId | string (uuid) | Yes | A Universally Unique Identifier used to uniquely identify entities in Meshery. The UUID core definition is used across different schemas. |
severity | string | Yes | Event level. MeshKit’s producers set one of emergency, alert, critical, error, warning, informational, debug or success. The set is not closed on the wire - the event write APIs persist the value they are given - so consumers must tolerate other values. |
status | string | Yes | Read state of the event. MeshKit records new events as unread, and acknowledged ones become read; the event status APIs persist any value they are given, so consumers must tolerate other values. |
systemId | string (uuid) | Yes | ID of the system instance that emitted the event. A Meshery Server sends its server instance ID; an event the provider emits itself carries the nil UUID. A client that registered a connection for its machine (for example a desktop client) sets its connection ID, so an event that records a run names the computer that ran it and can be joined to the claim it released (Claim.outcomeEventId) and to the connection (connections.id). The value is asserted by the sender and is not checked against the caller’s connections. |
updatedAt | string (date-time) | Yes | Timestamp when the event was last updated. |
visibility | string | Yes | Who can see the event. Defaults to private. |