Wildcard subject for all lattice events. Subscribe to this subject to receive all CloudEvent messages emitted by wasmCloud hosts in the lattice. Events are JSON-encoded CloudEvents with a type prefix of com.wasmcloud.lattice.
Emitted when a WebAssembly component's instance count is scaled up or down on a host.
Content-Type: application/json
ComponentStartFailed
Emitted when a wasmCloud host fails to start a WebAssembly component.
Content-Type: application/json
ProviderStarted
Emitted when a capability provider has successfully started on a host.
Content-Type: application/json
ProviderStopped
Emitted when a capability provider has stopped on a host.
Content-Type: application/json
ProviderStartFailed
Emitted when a wasmCloud host fails to start a capability provider.
Content-Type: application/json
LinkdefSet
Emitted when a link definition between a component and a provider or between two components is established in the lattice.
Content-Type: application/json
LinkdefDeleted
Emitted when a link definition is removed from the lattice.
Content-Type: application/json
ConfigSet
Emitted when a named configuration entry is created or updated in the lattice configuration store.
Content-Type: application/json
ConfigDeleted
Emitted when a named configuration entry is deleted from the lattice configuration store.
Content-Type: application/json
HostHeartbeat
Emitted periodically by each wasmCloud host containing a complete inventory of all components and providers running on that host.
Content-Type: application/json
HostStarted
Emitted when a new wasmCloud host joins the lattice.
Content-Type: application/json
HostStopped
Emitted when a wasmCloud host leaves the lattice gracefully.
Content-Type: application/json
HealthCheckPassed
Emitted when a capability provider passes its periodic health check.
Content-Type: application/json
HealthCheckFailed
Emitted when a capability provider fails its periodic health check.
Content-Type: application/json
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.