Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 4684472 (merge ref)

Garnet Python toolchain visibility/python-toolchain

run 31545378850

Execution chains

7 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • node[2463 · node]
        • results-receiver.actions.githubusercontent140.82.114.22:443 (https) · tcpalso recorded: glb-db52c2cf8be544.github.com
        • github.com140.82.114.4:443 (https) · tcp
        • release-assets.githubusercontent.com185.199.110.133:443 (https) · tcp
        • productionresultssa1.blob.core.windows.net20.209.226.129:443 (https) · tcpalso recorded: blob.blz25prdstrz09a.trafficmanager.net, blob.blz25prdstrz09a.store.core.windows
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[508 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1305 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Python toolchain visibility
Jobpython-toolchain
Run ID31545378850
Profile UUID019ff317-99e5-7d0d-bd9c-bb7631b50189
Commit SHA4684472341c83cfa1cc47e18a27665f46ec1ce62(merge ref)
Refrefs/pull/126/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