Execution Profile

garnet-labs/litellm

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

Garnet Runtime Visibility/extension-install

run 44023787555

Execution chains

5 destinations · 6 processes
  • systemd
    • hosted-compute-agent[1970 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker[2044 · Runner.Worker]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd4062970496[1987 · provjobd4062970496]
          • 140.82.113.24:443 (https) · tcp
      • 140.82.113.24:443 (https) · tcp
    • systemd-resolved[220 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.14
      • python3.14[1274 · python3.14]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-networkd[712 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobextension-install
Profile UUID01a1e7f6-f518-70dd-b2f7-5de901371eca
Refrefs/pull/147/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.