Execution Profile

garnet-labs/posthog

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

Garnet Runtime Visibility/gateway-install

run 41974578677

Execution chains

10 destinations · 6 processes
  • systemd
    • hosted-compute-
      • Runner.ListenerRunner.Worker
        • MainThread[2427 · 2485 · MainThread]
          • bash
            • python3.14[2459 · python3.14]step: <unknown>
              • dualstack.python.map.fastly.net140.248.144.223:443 (https) · tcpalso recorded: files.pythonhosted.org
              • pypi.org151.101.64.223:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • releases.astral.sh104.26.13.77:443 (https) · tcp
          • raw.githubusercontent.com185.199.110.133:443 (https) · tcp
          • api.github.com140.82.112.5:443 (https) · tcp
          • github.com140.82.114.4:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd6966337[1902 · provjobd6966337]
          • 20.75.202.224:443 (https) · tcp
    • systemd-resolve[431 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • python3
      • python3[1264 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobgateway-install
Profile UUID01a1aa32-9d04-7712-bd99-d18912490b65
Refrefs/pull/245/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.