Execution Profile

garnet-labs/posthog

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

Garnet Runtime Visibility/python-toolchain

run 31542501399

Execution chains

7 destinations · 4 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • node[2631 · node]
        • releases.astral.sh104.26.12.77:443 (https) · tcp
        • raw.githubusercontent.com185.199.108.133:443 (https) · tcp
        • productionresultssa1.blob.core.windows.net20.209.227.33:443 (https) · tcpalso recorded: blob.blz25prdstrz09a.trafficmanager.net, blob.blz25prdstrz09a.store.core.windows
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • python3.12
      • python3.12[1829 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[532 · 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
Run ID31542501399
Profile UUID019ff2f1-edb6-748e-83ec-18569c8fc116
Commit SHAdfb8754b0dd822c9ee24271b129e2857da7c2268(merge ref)
Refrefs/pull/111/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