Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 333f022 (merge ref)

Garnet Runtime Visibility/dashboard-install

run 44370263417

Execution chains

5 destinations · 6 processes
  • systemd
    • hosted-compute-[2029 · hosted-compute-]
      • Runner.Listener
        • Runner.Worker[2081 · Runner.Worker]
          • bash
            • node[2568 · node]
              • registry.npmjs.org104.16.11.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1668839[2047 · provjobd1668839]
          • 140.82.112.23:443 (https) · tcp
      • 140.82.114.23:443 (https) · tcp
    • Daemon
      • ExtHandler[1307 · ExtHandler]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolve[229 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Runtime Visibility
Jobdashboard-install
Profile UUID01a1efec-ff25-79b1-8e53-e8eddca38212
Refrefs/pull/162/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.