Execution Profile

garnet-labs/posthog

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

Garnet Runtime Visibility/clitools-requirements-install

run 41974615114

Execution chains

5 destinations · 4 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[1997 · Runner.Worker]
        • bash
          • python3.12[2469 · python3.12]
            • files.pythonhosted.org140.248.144.223:443 (https) · tcpalso recorded: dualstack.python.map.fastly.net
            • pypi.org151.101.192.223:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[439 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1245 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobclitools-requirements-install
Run ID41974615114
Profile UUID01a1aa50-8edd-7e1e-8646-e104d03ffe66
Commit SHAf3a7de0eeaa269465f8bb16a83392acb23ece80d(merge ref)
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.

Read the docs