Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 14b5962 (merge ref)

probe — IMDS recordability/probe

run 31130600090

Execution chains

8 destinations · 5 processes
  • systemd
    • hosted-compute-agent[1821 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker
          • bash
            • curl[2338 · curl]step: curl the metadata endpoint and a public endpoint
              • example.com104.20.23.154:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
            • node
              • node[2350 · node]step: node child process performs the same requests
                • example.com172.66.147.243:443 (https) · tcp
                • localhost127.0.0.53:53 (dns) · udp(dns resolver)
                • 169.254.169.254:80 (http) · tcp(cloud metadata)
            • curl[2336 · curl]step: curl the metadata endpoint and a public endpoint
              • 169.254.169.254:80 (http) · tcp(cloud metadata)
          • node[2300 · node]
            • api.github.com140.82.112.5:443 (https) · tcp
            • github.com140.82.114.4:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.109.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • 140.82.112.4:443 (https) · tcp
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
Run details
Repositorygarnet-labs/posthog
Workflowprobe — IMDS recordability
Jobprobe
Profile UUID019fd963-14f5-71df-8b37-e598603e0575
Refrefs/pull/84/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.