Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 176e8ed (merge ref)

Garnet Runtime Visibility/extension-install

run 44140667287

Execution chains

5 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2563 · node]step: Install extension dependencies
            • registry.npmjs.org104.16.9.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1564831798[1994 · provjobd1564831798]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • python3.14
      • python3.14[1324 · python3.14]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[227 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[723 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobextension-install
Profile UUID01a1ea9f-30b6-72a6-8d57-a3e91a9ef1c1
Refrefs/pull/149/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.