Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 6c9fcd9 (merge ref)

Garnet Runtime Visibility/dashboard-install

run 44022236579

Execution chains

10 destinations · 5 processes
  • systemd
    • hosted-compute-[1932 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2695 · node]
            • registry.npmjs.org104.16.7.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2650245[2184 · provjobd2650245]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • systemd-resolve[664 · systemd-resolve]
      • 10.0.0.2:53 (dns) · udp
    • chronyd-starter
      • chronyd[1368 · chronyd]
        • 169.254.169.123:123 (ntp) · udp
        • 185.125.190.122:123 (ntp) · udp
        • 185.125.190.123:123 (ntp) · udp
        • 91.189.91.111:123 (ntp) · udp
        • 91.189.91.112:123 (ntp) · udp
        • 91.189.91.113:123 (ntp) · udp
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobdashboard-install
Profile UUID01a1e7eb-6e31-7782-a1bc-2e56c54290c6
Refrefs/pull/146/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.