Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 4880a03 (merge ref)

Garnet Runtime Visibility/dashboard-install

run 44150629713

Execution chains

6 destinations · 6 processes
  • systemd
    • hosted-compute-agent[1858 · hosted-compute-agent]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2545 · node]step: Install dashboard dependencies
            • registry.npmjs.org104.16.8.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1037546940[1876 · provjobd1037546940]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • python3.14
      • python3.14[1313 · python3.14]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[220 · 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
Jobdashboard-install
Profile UUID01a1ead1-ce2b-74d1-a111-274ae83d4422
Refrefs/pull/154/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.