Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

WorkerLifecycleEvent

import type { WorkerLifecycleEvent } from "https://googleapis.deno.dev/v1/dataflow:v1b3.ts";

A report of an event in a worker's lifecycle. The proto contains one event, because the worker is expected to asynchronously send each message immediately after the event. Due to this asynchrony, messages may arrive out of order (or missing), and it is up to the consumer to interpret. The timestamp of the event is in the enclosing WorkerMessage proto.

interface WorkerLifecycleEvent {
containerStartTime?: Date;
event?:
| "UNKNOWN_EVENT"
| "OS_START"
| "CONTAINER_START"
| "NETWORK_UP"
| "STAGING_FILES_DOWNLOAD_START"
| "STAGING_FILES_DOWNLOAD_FINISH"
| "SDK_INSTALL_START"
| "SDK_INSTALL_FINISH";
metadata?: {
[key: string]: string;
};
}

§Properties

§
containerStartTime?: Date
[src]

The start time of this container. All events will report this so that events can be grouped together across container/VM restarts.

§
event?: "UNKNOWN_EVENT" | "OS_START" | "CONTAINER_START" | "NETWORK_UP" | "STAGING_FILES_DOWNLOAD_START" | "STAGING_FILES_DOWNLOAD_FINISH" | "SDK_INSTALL_START" | "SDK_INSTALL_FINISH"
[src]

The event being reported.

§
metadata?: {
[key: string]: string;
}
[src]

Other stats that can accompany an event. E.g. { "downloaded_bytes" : "123456" }