Execution Profile

garnet-labs/litellm

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

Garnet Runtime Visibility/dashboard-install

run 44362455947

Execution chains

7 destinations · 6 processes
  • systemd
    • hosted-compute-[1968 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2540 · node]
            • registry.npmjs.org104.16.8.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd8327234[1985 · provjobd8327234]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-gccus02-02.githubapp140.82.114.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
      • 140.82.112.23:443 (https) · tcp
    • systemd-resolve[225 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • Daemon
      • ExtHandler[1240 · ExtHandler]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-network[716 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobdashboard-install
Profile UUID01a1efc6-660a-7158-9e00-384c33fa066b
Refrefs/pull/161/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.