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

3 destinations · 3 processes
  • systemd
    • python3.12
      • python3.12[1448 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[515 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • hosted-compute-agentsudo
      • provjobd2134656144[2032 · provjobd2134656144]
        • 20.75.202.224:443 (https) · tcp
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobclitools-requirements-install
Run ID41974615114
Profile UUID01a1aa32-86e0-7866-85b0-de633b42547c
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