Execution Profile

garnet-labs/litellm

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

Garnet Runtime Visibility/dashboard-install

run 44350813793

Execution chains

8 destinations · 7 processes
  • systemd
    • hosted-compute-[2160 · hosted-compute-]
      • Runner.Listener
        • Runner.Worker[2243 · Runner.Worker]
          • bash
            • node[2758 · node]
              • registry.npmjs.org104.16.5.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1372522[2184 · provjobd1372522]
          • 140.82.114.23:443 (https) · tcp
      • 140.82.114.24:443 (https) · tcp
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • hosted-compute-request-orchestrator-prod-iad-02140.82.113.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • systemd-resolve[220 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • Daemon
      • ExtHandler[1456 · ExtHandler]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-network[793 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobdashboard-install
Profile UUID01a1ef8e-c786-7c1e-9027-87e2b3b297c6
Refrefs/pull/157/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.