> ## Documentation Index
> Fetch the complete documentation index at: https://na-36-changelog-go-livepeer-2026-05-18.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Operator Toolbox

> Every tool for monitoring, verifying, and operating your Livepeer orchestrator – Explorer, Prometheus metrics, Docker monitoring stack, community dashboards, and capability testing utilities.

Your node is running. These are the tools you reach for when you want to verify you are in the Active Set, track earnings, diagnose a routing problem, monitor GPU health, or understand what the network is doing.

## Livepeer Explorer

**URL:** [explorer.livepeer.org](https://explorer.livepeer.org)

The Explorer is the authoritative on-chain dashboard for the Livepeer Protocol. It reads directly from the Arbitrum subgraph, so everything you see here reflects current on-chain state.

**Your Orchestrator profile lives at:**

```text icon="terminal" title="Explorer orchestrator profile URL" theme={null}
https://explorer.livepeer.org/accounts/<your-address>/orchestrating
```

> **Active Set and Stake**
>
> See your rank by total stake (own + delegated). The top 100 active Orchestrators receive transcoding work. Check here to confirm you are in the set and track your rank trend.

> **Reward Call History**
>
> Round-by-round history of reward calls. Missed rounds mean lost inflation – for you and your Delegators. Target is 100% call rate. Any gaps here warrant investigation.

> **Earnings**
>
> Cumulative ETH transcoding fees and LPT inflation rewards. Use this to verify your node is earning and to track long-term trend.

> **Governance**
>
> Vote on Livepeer Improvement Proposals and treasury proposals directly from the Explorer interface.

**Also on the Explorer:**

* Your published Reward Cut and fee share – verify these match what you configured on-chain
* Your Delegator list, with individual stake amounts and unbonding status
* Rounds active (your seniority on the network)

> [!NOTE]
>
> The Explorer shows on-chain data only. Worker-level data for pool contributors lives outside Explorer, and off-chain pool payouts do not appear there. For AI model warm status, use [tools.Livepeer.cloud/ai/network-capabilities](https://tools.livepeer.cloud/ai/network-capabilities).

## Node Metrics (Prometheus)

go-livepeer exposes a standard Prometheus metrics endpoint. Scrape it with any monitoring stack.

**Enable metrics with the `-monitor` flag:**

```bash icon="terminal" title="Enable Prometheus metrics" theme={null}
livepeer \
  -orchestrator \
  -transcoder \
  -monitor \
  -metricsPerStream \
  # ... Other flags
```

**Flags:**

<table>
  <tr>
    Flag

    Effect
  </tr>

  <tr>
    `-monitor`

    Enables the `/metrics` endpoint on port 7935
  </tr>

  <tr>
    `-metricsPerStream`

    Groups performance metrics per stream – useful for debugging individual sessions
  </tr>

  <tr>
    `-metricsClientIP`

    Exposes client IP in metrics – useful for identifying which Gateway is sending work
  </tr>
</table>

**Endpoint:** `http://localhost:7935/metrics`

**Key metric categories exposed:**

* Session count and capacity utilisation
* Segment success and failure rates by stream
* Winning ticket counts (probabilistic approximation)
* Job processing latency
* GPU utilisation

For the full metric reference, see the [Prometheus Metrics Reference](/v2/Orchestrators/guides/monitoring-and-tooling/metrics-and-alerting).

### Docker monitoring stack (fastest setup)

Livepeer maintains a Docker image that bundles Prometheus and Grafana with starter dashboard templates:

```bash icon="terminal" title="Docker monitoring stack for a single node" theme={null}
# Single node
docker run --net=host \
  --env LP_MODE=standalone \
  --env LP_NODES=localhost:7935 \
  livepeer/monitoring:latest
```

```bash icon="terminal" title="Docker monitoring stack for multiple nodes" theme={null}
# Multi-node
docker run --net=host \
  --env LP_MODE=standalone \
  --env LP_NODES=node1.example.com:7935,node2.example.com:7935 \
  livepeer/monitoring:latest
```

**Environment variable options:**

<table>
  <tr>
    Variable

    Values

    Description
  </tr>

  <tr>
    `LP_MODE`

    `standalone`, `docker-compose`, `kubernetes`

    Deployment mode
  </tr>

  <tr>
    `LP_NODES`

    Comma-separated `host:port` list

    Nodes to monitor
  </tr>

  <tr>
    `LP_KUBE_NAMESPACES`

    Comma-separated namespaces

    For Kubernetes deployments
  </tr>
</table>

For Kubernetes, pods with the `prometheus.io/scrape` label are discovered automatically.

> **[livepeer/livepeer-monitoring](https://github.com/livepeer/livepeer-monitoring)**
>
> Source, Dockerfile, and Prometheus.yml for the monitoring supercontainer.

### Custom Prometheus setup

Add this to your `prometheus.yml` to scrape go-livepeer directly:

```yaml icon="terminal" title="Prometheus scrape config" theme={null}
scrape_configs:
  - job_name: 'livepeer'
    static_configs:
      - targets: ['localhost:7935']
    scrape_interval: 15s
```

## Cloud SPE Tools

**URL:** [tools.Livepeer.cloud](https://tools.livepeer.cloud)

A community-built suite of Orchestrator and network monitoring tools, maintained by the Cloud SPE.

**Key sections:**

* **AI network capabilities** (`/ai/network-capabilities`) – lists all AI-capable Orchestrators by pipeline, showing which models are warm. Use this to verify your AI pipeline registrations are visible to the network after configuring `aiModels.json`.
* **Payout reports** – daily, weekly, and monthly earnings breakdowns per Orchestrator address
* **Orchestrator view** – per-Orchestrator statistics including pricing and job activity

> [!WARNING]
>
> This is community infrastructure maintained outside the Livepeer Foundation. It has experienced intermittent availability, so keep Explorer and Prometheus in the loop as primary sources.

## Network Dashboards (Dune Analytics)

For protocol-level macro data – inflation, staking participation, fee volumes, token distribution:

<table>
  <tr>
    Dashboard

    Link
  </tr>

  <tr>
    Growth Dashboard

    [dune.com/rickstaa/livepeer-growth-dashboard](https://dune.com/rickstaa/livepeer-growth-dashboard)
  </tr>

  <tr>
    Governance Dashboard

    [dune.com/rickstaa/livepeer-governance-dashboard](https://dune.com/rickstaa/livepeer-governance-dashboard)
  </tr>

  <tr>
    Token Dashboard (Arbitrum)

    [dune.com/stronk/livepeer-Arbitrum](https://dune.com/stronk/livepeer-arbitrum)
  </tr>
</table>

Use these dashboards for network trends. Use Explorer and Prometheus for per-node operations.

## Capability Testing

Tools for verifying your node is correctly serving jobs end-to-end. Use them to confirm behaviour from the outside instead of inferring everything from logs.

> **[stream-tester](https://github.com/livepeer/stream-tester)**
>
> Submits transcoding jobs to an Orchestrator and measures response times and success rates. Used to validate your transcoding capability from the outside.

> **[livepeer-ai-job-tester](https://github.com/mikezupper/livepeer-ai-job-tester)**
>
> Community-built tool (Cloud SPE) that submits AI inference jobs and records performance metrics. Used to verify AI pipeline availability before relying on network routing.

## Tool selection guide

<table>
  <tr>
    Situation

    Tool to reach for
  </tr>

  <tr>
    Am I in the Active Set?

    Livepeer Explorer → Orchestrator list
  </tr>

  <tr>
    Did I miss any reward rounds?

    Livepeer Explorer → reward call history
  </tr>

  <tr>
    Is my node processing jobs right now?

    Prometheus `/metrics` → session count; or `-v 6` logs
  </tr>

  <tr>
    Why am I not receiving AI jobs?

    tools.Livepeer.cloud/ai/network-capabilities
  </tr>

  <tr>
    Is my transcoding pipeline working correctly?

    stream-tester
  </tr>

  <tr>
    What is the network-wide inflation rate?

    Dune dashboards
  </tr>

  <tr>
    Is my pricing competitive?

    Explorer → compare your price to top 20 Orchestrators
  </tr>
</table>

> **[Livepeer Explorer Guide](/v2/orchestrators/guides/monitoring-and-tooling/explorer-operations)**
>
> Full walkthrough of every Explorer metric and what to do when things look wrong.

> **[Metrics and Monitoring](/v2/orchestrators/guides/monitoring-and-tooling/metrics-and-alerting)**
>
> Setting up Prometheus, Grafana, and the Docker monitoring stack.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.