Execution Profile

garnet-labs/litellm

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

Garnet Runtime Visibility/dashboard-install

run 44140667287

Execution chains

12 destinations · 6 processes
  • systemd
    • hosted-compute-[2086 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2697 · node]step: Install dashboard dependencies
            • registry.npmjs.org104.16.3.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2891015[2183 · provjobd2891015]
          • 140.82.112.24:443 (https) · tcp
      • 140.82.112.24:443 (https) · tcp
      • 140.82.114.23:443 (https) · tcp
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolve[672 · systemd-resolve]
      • 10.0.0.2:53 (dns) · udp
    • chronyd-starter
      • chronyd[1380 · 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
    • systemd-network[1093 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobdashboard-install
Profile UUID01a1eaab-a7bd-7a3c-829c-b5c0397f382e
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.