build: run docs regen in synth.py (#1059)
diff --git a/docs/dyn/dataflow_v1b3.projects.html b/docs/dyn/dataflow_v1b3.projects.html
index 2047f0f..bb0f93b 100644
--- a/docs/dyn/dataflow_v1b3.projects.html
+++ b/docs/dyn/dataflow_v1b3.projects.html
@@ -149,8 +149,53 @@
The object takes the form of:
{ # A request for sending worker messages to the service.
+ "location": "A String", # The [regional endpoint] (https://cloud.google.com/dataflow/docs/concepts/regional-endpoints) that contains the job.
"workerMessages": [ # The WorkerMessages to send.
{ # WorkerMessage provides information to the backend about a worker.
+ "workerMetrics": { # Worker metrics exported from workers. This contains resource utilization metrics accumulated from a variety of sources. For more information, see go/df-resource-signals. # Resource metrics reported by workers.
+ "containers": { # Per container information. Key: container name.
+ "a_key": # Object with schema name: ResourceUtilizationReport
+ },
+ "memoryInfo": [ # Memory utilization samples.
+ { # Information about the memory usage of a worker or a container within a worker.
+ "currentLimitBytes": "A String", # Instantenous memory limit in bytes.
+ "currentRssBytes": "A String", # Instantenous memory (RSS) size in bytes.
+ "timestamp": "A String", # Timestamp of the measurement.
+ "totalGbMs": "A String", # Total memory (RSS) usage since start up in GB * ms.
+ },
+ ],
+ "cpuTime": [ # CPU utilization samples.
+ { # Modeled after information exposed by /proc/stat.
+ "timestamp": "A String", # Timestamp of the measurement.
+ "rate": 3.14, # Average CPU utilization rate (% non-idle cpu / second) since previous sample.
+ "totalMs": "A String", # Total active CPU time across all cores (ie., non-idle) in milliseconds since start-up.
+ },
+ ],
+ },
+ "workerHealthReport": { # WorkerHealthReport contains information about the health of a worker. The VM should be identified by the labels attached to the WorkerMessage that this health ping belongs to. # The health of a worker.
+ "pods": [ # The pods running on the worker. See: http://kubernetes.io/v1.1/docs/api-reference/v1/definitions.html#_v1_pod This field is used by the worker to send the status of the indvidual containers running on each worker.
+ {
+ "a_key": "", # Properties of the object.
+ },
+ ],
+ "vmStartupTime": "A String", # The time the VM was booted.
+ "reportInterval": "A String", # The interval at which the worker is sending health reports. The default value of 0 should be interpreted as the field is not being explicitly set by the worker.
+ "vmIsHealthy": True or False, # Whether the VM is currently healthy.
+ "msg": "A String", # A message describing any unusual health reports.
+ "vmIsBroken": True or False, # Whether the VM is in a permanently broken state. Broken VMs should be abandoned or deleted ASAP to avoid assigning or completing any work.
+ },
+ "workerMessageCode": { # A message code is used to report status and error messages to the service. The message codes are intended to be machine readable. The service will take care of translating these into user understandable messages if necessary. Example use cases: 1. Worker processes reporting successful startup. 2. Worker processes reporting specific errors (e.g. package staging failure). # A worker message code.
+ "parameters": { # Parameters contains specific information about the code. This is a struct to allow parameters of different types. Examples: 1. For a "HARNESS_STARTED" message parameters might provide the name of the worker and additional data like timing information. 2. For a "GCS_DOWNLOAD_ERROR" parameters might contain fields listing the GCS objects being downloaded and fields containing errors. In general complex data structures should be avoided. If a worker needs to send a specific and complicated data structure then please consider defining a new proto and adding it to the data oneof in WorkerMessageResponse. Conventions: Parameters should only be used for information that isn't typically passed as a label. hostname and other worker identifiers should almost always be passed as labels since they will be included on most messages.
+ "a_key": "", # Properties of the object.
+ },
+ "code": "A String", # The code is a string intended for consumption by a machine that identifies the type of message being sent. Examples: 1. "HARNESS_STARTED" might be used to indicate the worker harness has started. 2. "GCS_DOWNLOAD_ERROR" might be used to indicate an error downloading a GCS file as part of the boot process of one of the worker containers. This is a string and not an enum to make it easy to add new codes without waiting for an API change.
+ },
+ "labels": { # Labels are used to group WorkerMessages. For example, a worker_message about a particular container might have the labels: { "JOB_ID": "2015-04-22", "WORKER_ID": "wordcount-vm-2015…" "CONTAINER_TYPE": "worker", "CONTAINER_ID": "ac1234def"} Label tags typically correspond to Label enum values. However, for ease of development other strings can be used as tags. LABEL_UNSPECIFIED should not be used here.
+ "a_key": "A String",
+ },
+ "workerShutdownNotice": { # Shutdown notification from workers. This is to be sent by the shutdown script of the worker VM so that the backend knows that the VM is being shut down. # Shutdown notice by workers.
+ "reason": "A String", # The reason for the worker shutdown. Current possible values are: "UNKNOWN": shutdown reason is unknown. "PREEMPTION": shutdown reason is preemption. Other possible reasons may be added in the future.
+ },
"workerLifecycleEvent": { # 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. # Record of worker lifecycle events.
"containerStartTime": "A String", # The start time of this container. All events will report this so that events can be grouped together across container/VM restarts.
"metadata": { # Other stats that can accompany an event. E.g. { "downloaded_bytes" : "123456" }
@@ -158,54 +203,9 @@
},
"event": "A String", # The event being reported.
},
- "workerShutdownNotice": { # Shutdown notification from workers. This is to be sent by the shutdown script of the worker VM so that the backend knows that the VM is being shut down. # Shutdown notice by workers.
- "reason": "A String", # The reason for the worker shutdown. Current possible values are: "UNKNOWN": shutdown reason is unknown. "PREEMPTION": shutdown reason is preemption. Other possible reasons may be added in the future.
- },
"time": "A String", # The timestamp of the worker_message.
- "workerMetrics": { # Worker metrics exported from workers. This contains resource utilization metrics accumulated from a variety of sources. For more information, see go/df-resource-signals. # Resource metrics reported by workers.
- "cpuTime": [ # CPU utilization samples.
- { # Modeled after information exposed by /proc/stat.
- "timestamp": "A String", # Timestamp of the measurement.
- "totalMs": "A String", # Total active CPU time across all cores (ie., non-idle) in milliseconds since start-up.
- "rate": 3.14, # Average CPU utilization rate (% non-idle cpu / second) since previous sample.
- },
- ],
- "containers": { # Per container information. Key: container name.
- "a_key": # Object with schema name: ResourceUtilizationReport
- },
- "memoryInfo": [ # Memory utilization samples.
- { # Information about the memory usage of a worker or a container within a worker.
- "currentLimitBytes": "A String", # Instantenous memory limit in bytes.
- "timestamp": "A String", # Timestamp of the measurement.
- "currentRssBytes": "A String", # Instantenous memory (RSS) size in bytes.
- "totalGbMs": "A String", # Total memory (RSS) usage since start up in GB * ms.
- },
- ],
- },
- "labels": { # Labels are used to group WorkerMessages. For example, a worker_message about a particular container might have the labels: { "JOB_ID": "2015-04-22", "WORKER_ID": "wordcount-vm-2015…" "CONTAINER_TYPE": "worker", "CONTAINER_ID": "ac1234def"} Label tags typically correspond to Label enum values. However, for ease of development other strings can be used as tags. LABEL_UNSPECIFIED should not be used here.
- "a_key": "A String",
- },
- "workerMessageCode": { # A message code is used to report status and error messages to the service. The message codes are intended to be machine readable. The service will take care of translating these into user understandable messages if necessary. Example use cases: 1. Worker processes reporting successful startup. 2. Worker processes reporting specific errors (e.g. package staging failure). # A worker message code.
- "code": "A String", # The code is a string intended for consumption by a machine that identifies the type of message being sent. Examples: 1. "HARNESS_STARTED" might be used to indicate the worker harness has started. 2. "GCS_DOWNLOAD_ERROR" might be used to indicate an error downloading a GCS file as part of the boot process of one of the worker containers. This is a string and not an enum to make it easy to add new codes without waiting for an API change.
- "parameters": { # Parameters contains specific information about the code. This is a struct to allow parameters of different types. Examples: 1. For a "HARNESS_STARTED" message parameters might provide the name of the worker and additional data like timing information. 2. For a "GCS_DOWNLOAD_ERROR" parameters might contain fields listing the GCS objects being downloaded and fields containing errors. In general complex data structures should be avoided. If a worker needs to send a specific and complicated data structure then please consider defining a new proto and adding it to the data oneof in WorkerMessageResponse. Conventions: Parameters should only be used for information that isn't typically passed as a label. hostname and other worker identifiers should almost always be passed as labels since they will be included on most messages.
- "a_key": "", # Properties of the object.
- },
- },
- "workerHealthReport": { # WorkerHealthReport contains information about the health of a worker. The VM should be identified by the labels attached to the WorkerMessage that this health ping belongs to. # The health of a worker.
- "vmIsBroken": True or False, # Whether the VM is in a permanently broken state. Broken VMs should be abandoned or deleted ASAP to avoid assigning or completing any work.
- "pods": [ # The pods running on the worker. See: http://kubernetes.io/v1.1/docs/api-reference/v1/definitions.html#_v1_pod This field is used by the worker to send the status of the indvidual containers running on each worker.
- {
- "a_key": "", # Properties of the object.
- },
- ],
- "msg": "A String", # A message describing any unusual health reports.
- "vmStartupTime": "A String", # The time the VM was booted.
- "vmIsHealthy": True or False, # Whether the VM is currently healthy.
- "reportInterval": "A String", # The interval at which the worker is sending health reports. The default value of 0 should be interpreted as the field is not being explicitly set by the worker.
- },
},
],
- "location": "A String", # The [regional endpoint] (https://cloud.google.com/dataflow/docs/concepts/regional-endpoints) that contains the job.
}
x__xgafv: string, V1 error format.