Capture Worker Debug Data
A 3-step recipe with Google Cloud Dataflow. We can help you get access.
Recipe · 3 steps
Capture Worker Debug Data
Confirm a job, get its debug config, and send a debug capture.
- Read the job to confirm it exists before requesting debug configuration for one of its worker components.
- Retrieve the debug configuration for the targeted worker and component of the job.
- Submit the encoded debug capture payload for the same worker component as raw data.
What you'll need to have ready
- accessToken: Google Cloud OAuth 2.0 access token used as a Bearer credential.
- projectId: The Google Cloud project id that owns the job.
- location: The regional endpoint that contains the job (e.g. us-central1).
- jobId: The id of the job whose worker debug data is being captured.
- workerId: The worker id that generated the debug data.
- componentId: The internal component id for which debug data is captured.
- data: The encoded debug data to submit.
For your developer
Arazzo workflow google-cloud-dataflow:capture-worker-debug-data, 3 operations: getLocationJob → getLocationJobDebugConfig → sendLocationJobDebugCapture. Specs on APIs.io.