Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 788ea84 (merge ref)

Garnet Runtime Visibility/python-toolchain

run 31544754209

Execution chains

9 destinations · 5 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker
        • node[2542 · node]
          • glb-db52c2cf8be544.github.com140.82.112.22:443 (https) · tcpalso recorded: results-receiver.actions.githubusercontent
          • github.com140.82.113.3:443 (https) · tcp
          • release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • node[2571 · node]
          • productionresultssa0.blob.core.windows.net20.209.227.33:443 (https) · tcpalso recorded: blob.blz25prdstrz09a.trafficmanager.net, blob.blz25prdstrz09a.store.core.windows
    • python3.12
      • python3.12[1248 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[523 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[739 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobpython-toolchain
Profile UUID019ff30f-091b-7d99-b5e8-d2d5cc616dd8
Refrefs/pull/125/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.