Execution Profile

garnet-labs/posthog

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

Garnet Runtime Visibility/acceptance-requirements-install

run 41974578677

Execution chains

5 destinations · 5 processes
  • systemd
    • hosted-compute-agent[2060 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker[2159 · Runner.Worker]
          • bash
            • python3.12[2679 · python3.12]
              • dualstack.python.map.fastly.net151.101.0.223:443 (https) · tcpalso recorded: files.pythonhosted.org
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • 140.82.114.24:443 (https) · tcp
    • python3.12
      • python3.12[1469 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[556 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobacceptance-requirements-install
Run ID41974578677
Profile UUID01a1aa50-b7bd-75cc-bace-593128465bc8
Commit SHAf78e5113e9a321ad180d9c554bea4b9b63a3078f(merge ref)
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.

Read the docs