Execution Profile

garnet-labs/litellm

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

Garnet Runtime Visibility/extension-install

run 44362455947

Execution chains

4 destinations · 4 processes
  • systemd
    • hosted-compute-agentsudo
      • provjobd3230191755[1984 · provjobd3230191755]
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • hosted-compute-watchdog-gccus02-01.githubapp140.82.112.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • python3.14
      • python3.14[1278 · python3.14]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[222 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[716 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobextension-install
Profile UUID01a1efc5-bb50-7644-9f57-05616dcffa2a
Refrefs/pull/161/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.