Execution Profile

garnet-labs/airbyte

Recorded at the kernel by Garnetfor commit 032a496 (merge ref)

Connector CI/non-jvm-connectors-test

run 42951698822

Execution chains

3 destinations · 3 processes
  • systemd
    • hosted-compute-agentsudo
      • provjobd3518902696[1897 · provjobd3518902696]
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • hosted-compute-watchdog-prod-iad-01.githubapp140.82.113.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • python3.12
      • python3.12[1204 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[421 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/airbyte
WorkflowConnector CI
Jobnon-jvm-connectors-test
Run ID42951698822
Profile UUID01a1c89d-0ae1-7592-8ad2-4b893b631791
Commit SHA032a496ec443d8280a0633c29724c27162dadf49(merge ref)
Refrefs/pull/1/merge
Timestamp

The record is egress-centric; processes without recorded egress do not appear.

Put the record on your pull requests

Garnet records what your code actually did when it ran — one step in your GitHub Actions workflow.

Read the docs