Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 6dfa0e0 (merge ref)

Garnet Runtime Visibility/gateway-install

run 43163742256

Execution chains

11 destinations · 6 processes
  • systemd
    • hosted-compute-Runner.Listener
      • Runner.Worker
        • node[2711 · 2767 · node]
          • bash
            • python3.14[2742 · python3.14]
              • pypi.org151.101.0.223:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • releases.astral.sh104.26.12.77:443 (https) · tcp
          • 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)
        • bash
          • uv[2791 · uv]
            • pypi.org151.101.0.223:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • python3
      • python3[2077 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-network[730 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobgateway-install
Run ID43163742256
Profile UUID01a1ce4d-c0f8-7cf5-a292-04fe1966d4d2
Commit SHA6dfa0e0f2b3d10e44da09c4ce198da2dc6bf9f77(merge ref)
Refrefs/pull/260/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