Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 2566be6 (merge ref)

Garnet Runtime Visibility/gateway-install

run 419746029642026-11-05 06:06 UTC

Execution chains

8 destinations · 7 processes

systemd
- hosted-compute-[1903 · hosted-compute-]
  - Runner.Listener
    - Runner.Worker[2006 · Runner.Worker]
      - node[2447 · 2504 · node]
        bash
        python3.14[2479 · python3.14]step: <unknown>
        pypi.org151.101.0.223:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
        api.github.com140.82.112.5:443 (https) · tcp
        github.com140.82.114.4:443 (https) · tcp
        release-assets.githubusercontent.com185.199.111.133:443 (https) · tcp
        releases.astral.sh172.67.68.3:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - 20.75.202.224:443 (https) · tcp
- systemd-resolve[438 · systemd-resolve]
  - 168.63.129.16:53 (dns) · udp
- python3
  - python3[1246 · python3]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-labs/posthog

WorkflowGarnet Runtime Visibility

Jobgateway-install

Run ID41974602964

Profile UUID01a1aa50-e7d9-75a8-add6-a09a481b1d00

Commit SHA2566be69029eea77de614ca8f71b721b2edd0c55(merge ref)

Refrefs/pull/246/merge

Timestamp2026-11-05 06:06:15 UTC

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.