{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/5de72ffb97d7409db292119aada1218b\" frameborder=\"0\" width=\"1114\" height=\"835\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":835,"width":1114,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":835,"thumbnail_width":1114,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/5de72ffb97d7409db292119aada1218b-6244858f6078dde0.gif","duration":138.353,"title":"Collecting Telemetry From Cloud Agent Sessions","description":"This Loom demonstrates how Asymptote’s open source AgentBeacon collects and persists telemetry from cloud agent sessions. Justin shows a Cloud Code environment (“Asymptote Tracing”) configured via docs with network allowlisting, Beacon-specific environment variables, object storage parameters, and a setup script that installs the Beacon binary. After running an agent prompt that reads the AgentBeacon README, executes commands, and summarizes the actions, he verifies the collected trace in a GCS bucket. He downloads and opens the trace execution JSON, noting it contains rich metadata such as the submitted prompt."}