Execution Profile

garnet-labs/posthog

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

Garnet Runtime Visibility/gateway-install

run 41974615114

Execution chains

10 destinations · 7 processes
  • systemd
    • hosted-compute-[1881 · hosted-compute-]
      • Runner.Listener
        • Runner.Worker
          • node[2483 · node]
            • bash
              • python3.14[2516 · python3.14]
                • pypi.org151.101.128.223:443 (https) · tcp
                • localhost127.0.0.53:53 (dns) · udp(dns resolver)
            • github.com140.82.113.4:443 (https) · tcp
            • api.github.com140.82.114.5:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • bash
            • uv[2565 · uv]
              • pypi.org151.101.128.223:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • sudo[1898 · sudo]
          • 140.82.112.23:443 (https) · tcp
      • 140.82.114.24:443 (https) · tcp
    • python3
      • python3[1861 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolve[466 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobgateway-install
Profile UUID01a1aa50-facb-7d52-aec7-4dabdf711745
Refrefs/pull/247/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.