Giter Site home page Giter Site logo

transcodeninja / livepeer-exporter Goto Github PK

View Code? Open in Web Editor NEW
0.0 1.0 0.0 6.06 MB

A Prometheus exporter for Livepeer orchestrator metrics. Fetches and exposes orchestrator metrics from various Livepeer endpoints for Prometheus to scrape.

Home Page: https://hub.docker.com/r/rickstaa/livepeer-exporter

License: MIT License

Dockerfile 0.87% Go 99.13%
exporter livepeer orchestrator prometheus prometheus-exporter transcoding

livepeer-exporter's Introduction

Livepeer Exporter

image

Livepeer Exporter is a lightweight tool designed to enhance the monitoring capabilities of Livepeer. As a Prometheus exporter, it fetches various metrics from different Livepeer endpoints and exposes them via an HTTP server, ready for Prometheus to scrape. It streamlines the Prometheus scraping process by eliminating the sluggish data extraction through Grafana plugins like marcusolsson-json-datasource and yesoreyeram-infinity-datasource. This makes it the perfect companion to the Livepeer monitoring service, extending the range of Livepeer metrics that can be monitored. By providing deeper insights into Livepeer's performance, Livepeer Exporter helps users optimize their streaming workflows and ensure reliable service delivery. Witness it in action by exploring the Grafana dashboards of the transcode.eth orchestrator.

Configuration

Before using the Livepeer Exporter, you must configure it using environment variables. These variables allow you to customize the behaviour of the exporter to suit your specific needs. Below, you'll find a list of all the environment variables you can set, a description of what they do, and their default values if they are not specified.

Required environment variables

  • LIVEPEER_EXPORTER_ORCHESTRATOR_ADDRESS: The address of the orchestrator to fetch data for.

Optional environment variables

  • LIVEPEER_EXPORTER_ORCHESTRATOR_ADDRESS_SECONDARY: The address of the secondary orchestrator to include in the data fetching. Used to calculate the livepeer_orch_stake metric. When set, the LPT stake of this address is added to the LPT stake that the orchestrator bonds.
  • LIVEPEER_EXPORTER_INFO_FETCH_INTERVAL: How often to fetch general orchestrator information. Defaults to 2m.
  • LIVEPEER_EXPORTER_SCORE_FETCH_INTERVAL: How often to fetch score data for the orchestrator. Defaults to 15m.
  • LIVEPEER_EXPORTER_DELEGATORS_FETCH_INTERVAL: How often to fetch delegators data for the orchestrator. Defaults to 15m.
  • LIVEPEER_EXPORTER_TEST_STREAMS_FETCH_INTERVAL:How often to fetch the test streams data for the orchestrator. Defaults to 15m.
  • LIVEPEER_EXPORTER_TICKETS_FETCH_INTERVAL: How often to fetch ticket data for the orchestrator. Defaults to 15m.
  • LIVEPEER_EXPORTER_REWARDS_FETCH_INTERVAL: How often to fetch rewards data for the orchestrator. Defaults to 15m.
  • LIVEPEER_EXPORTER_CRYPTO_PRICES_FETCH_INTERVAL: How often to fetch the crypto prices. Defaults to 1m.
  • LIVEPEER_EXPORTER_INFO_UPDATE_INTERVAL: How often to update the orchestrator info metrics. Defaults to 1m.
  • LIVEPEER_EXPORTER_SCORE_UPDATE_INTERVAL: How often to update the orchestrator score metrics. Defaults to 1m.
  • LIVEPEER_EXPORTER_DELEGATORS_UPDATE_INTERVAL: How often to update the orchestrator delegators metrics. Defaults to 1m.
  • LIVEPEER_EXPORTER_TEST_STREAMS_UPDATE_INTERVAL: How often to update the orchestrator test streams metrics. Defaults to 1m.
  • LIVEPEER_EXPORTER_TICKETS_UPDATE_INTERVAL: How often to update the orchestrator tickets metrics. Defaults to 1m.
  • LIVEPEER_EXPORTER_REWARDS_UPDATE_INTERVAL: How often to update the orchestrator rewards metrics. Defaults to 1m.
  • LIVEPEER_EXPORTER_CRYPTO_PRICES_UPDATE_INTERVAL: How often to update the crypto prices metrics. Defaults to 1m.

All intervals are specified as a string representation of a duration, e.g., 5m for 5 minutes, 2h for 2 hours, etc. See time#ParseDuration for format details.

Important

Please be respectful when setting the fetch intervals. Setting these values to low will cause unnecessary load on the Livepeer infrastructure. If you are unsure what values to use, please use the defaults. Thanks for your understanding ❤️!

Usage

This section explains how to run the Livepeer Exporter. You can run it locally on your machine or use Docker for easy setup and teardown.

Run exporter locally

Running the exporter on your main OS allows you to test out the livepeer-exporter quickly. You must set the necessary environment variables and start the exporter to do this. Replace your-orchestrator-address with your values:

export LIVEPEER_EXPORTER_ORCHESTRATOR_ADDRESS=your-orchestrator-address
go run main.go

The exporter will be available on port 9153. Additional configuration environment variables can be passed to the exporter by adding them to the command above.

Running the Exporter with Docker

You can run the exporter using the Docker image available on Docker Hub. To pull and run the exporter from Docker Hub, use the following command:

docker run --name livepeer-exporter \
    -e "LIVEPEER_EXPORTER_ORCHESTRATOR_ADDRESS=<your-orchestrator-address>" \
    -p 9153:9153 \
    transcodeninja/livepeer-exporter:latest

Replace <your-orchestrator-address> with the address of your orchestrator. This command will start the exporter and expose the metrics on port 9153 for Prometheus to scrape. This command will start the exporter and expose the metrics on port 9153 for Prometheus to scrape. Additional environment variables can be passed to the exporter by adding them to the command above.

Note

This repository also contains a DockerFile and docker-compose.yml file. These files can be used to build and run the exporter locally. To do this, clone this repository and run docker compose up in the repository's root directory.

Configure Prometheus

For Prometheus to scrape the exporter, add the following to your prometheus.yml:

scrape_configs:
  - job_name: livepeer-exporter
    static_configs:
      - targets: ["localhost:9153"]

This configuration tells Prometheus to scrape metrics from the Livepeer Exporter running on localhost port 9153.

Metrics

This exporter comprises the following sub-exporters, each responsible for fetching specific metrics:

Sub-Exporter Description
orch_info_exporter Collects metrics pertaining to the Livepeer orchestrator.
orch_score_exporter Retrieves metrics concerning the Livepeer orchestrator's score.
orch_delegators_exporter Gathers metrics related to the delegators of the designated Livepeer orchestrator.
orch_test_streams_exporter Procures metrics about the Livepeer orchestrator's test streams.
orch_tickets_exporter Fetches metrics about the Livepeer orchestrator's tickets.
orch_reward_exporter Retrieves metrics about the Livepeer orchestrator's rewards.
crypto_prices_exporter Fetches and exposes the prices of different cryptocurrencies used in the Livepeer ecosystem.

For enhanced performance, these sub-exporters operate concurrently in separate goroutines. They fetch metrics from various Livepeer endpoints and expose them via the 9153/metrics endpoint. For detailed information about these sub-exporters and the metrics they provide, refer to the sections below.

Crypto Prices Exporter

The crypto_prices_exporter fetches and exposes the prices of different cryptocurrencies used in the Livepeer ecosystem. They include:

GaugeVec metrics:

  • LPT_price: This metric denotes the present value of the LPT token. It incorporates the currency label to denote the used currency (e.g., USD, EUR, etc.).
  • ETH_price: This metric denotes the current price of Ethereum. It incorporates the currency label to denote the used currency (e.g., USD, EUR, etc.).

orch_delegators_exporter

The orch_delegators_exporter fetches metrics about the delegators of the set Livepeer orchestrator from the Livepeer subgraph endpoint. These metrics provide insights into the number and behaviour of the delegators that stake with the orchestrator. They include:

Gauge metrics:

  • livepeer_orch_delegator_count: This metric represents the total number of delegators that stake with the Livepeer orchestrator.

GaugeVec metrics:

  • livepeer_orch_delegator_bonded_amount: This metric represents the bonded LPT amount associated with each delegator. It includes the id label representing the delegator address.
  • livepeer_orch_delegator_start_round: This metric represents the start round for each delegator. It includes the id label representing the delegator's address.
  • livepeer_orch_delegator_collected_fees: This metric represents the ETH fees collected by each delegator. It includes the id label representing the delegator address.

orch_info_exporter

The orch_info_exporter fetches metrics about the Livepeer orchestrator from the Livepeer Orchestrator API and Livepeer Delegating API endpoints. These metrics provide insights into the orchestrator's performance and behaviour. They include:

Gauge metrics:

  • livepeer_orch_bonded_amount: This metric represents the amount of LPT bonded to the orchestrator.
  • livepeer_orch_total_stake: This metric represents the total amount of LPT staked with the orchestrator.
  • livepeer_orch_last_reward_claim_round: This metric represents the last round in which the orchestrator claimed the reward.
  • livepeer_orch_start_round: This metric represents the round the orchestrator registered.
  • livepeer_orch_withdrawn_fees: This metric represents the ETH fees the orchestrator has withdrawn.
  • livepeer_orch_current_round: This metric represents the current round.
  • livepeer_orch_activation_round: This metric represents the round the orchestrator activated.
  • livepeer_orch_active: This metric represents whether the orchestrator is active.
  • livepeer_orch_fee_cut: This metric represents the proportion of the fees the orchestrator takes.
  • livepeer_orch_reward_cut: This metric represents the proportion of the block reward the orchestrator takes.
  • livepeer_orch_last_reward_round: This metric represents the last round in which the orchestrator received rewards while active.
  • livepeer_orch_ninety_day_volume_eth: This metric represents the 90-day volume of ETH.
  • livepeer_orch_thirty_day_volume_eth: This metric represents the 30-day volume of ETH.
  • livepeer_orch_total_volume_eth: This metric represents the total volume of ETH.
  • livepeer_orch_stake: This metric reflects the quantity of LPT personally contributed by the orchestrator, encompassing the orchestrator's bonded stake and, if provided, the stake from the secondary orchestrator account.
  • livepeer_orch_thirty_day_reward_claim_ratio: This metric represents how often an orchestrator claimed rewards in the last thirty rounds, or, if not active for 30 days, the reward claim ratio since activation.

orch_rewards_exporter

The orch_rewards_exporter fetches reward data for the Livepeer orchestrator from the Livepeer subgraph endpoint. These metrics provide insights into the rewards the orchestrator claims. They include:

Gauge metrics:

  • livepeer_orch_day_rewards: This metric represents the LPT rewards claimed by the orchestrator in the last 24 hours.
  • livepeer_orch_week_rewards: This metric represents the LPT rewards claimed by the orchestrator in the last 7 days.
  • livepeer_orch_thirty_day_rewards: This metric represents the LPT rewards claimed by the orchestrator in the last 30 days.
  • livepeer_orch_ninety_day_rewards: This metric represents the LPT rewards claimed by the orchestrator in the last 90 days.
  • livepeer_orch_year_rewards: This metric represents the LPT rewards claimed by the orchestrator in the last 365 days.
  • livepeer_orch_total_rewards: This metric represents the total rewards claimed by the orchestrator.
  • livepeer_orch_rewards_day_gas_cost: This metric represents the gas cost of the reward transactions in the last 24 hours.
  • livepeer_orch_rewards_week_gas_cost: This metric represents the gas cost of the reward transactions in the last 7 days.
  • livepeer_orch_rewards_thirty_day_gas_cost: This metric represents the gas cost of the reward transactions in the last 30 days.
  • livepeer_orch_rewards_ninety_day_gas_cost: This metric represents the gas cost of the reward transactions in the last 90 days.
  • livepeer_orch_rewards_year_gas_cost: This metric represents the gas cost of the reward transactions in the last 365 days.
  • livepeer_orch_rewards_total_gas_cost: This metric represents the total gas cost of the reward transactions.

GaugeVec metrics:

  • livepeer_orch_reward_amount: This metric represents the LPT rewards claimed in each reward transaction. It includes the id label representing the transaction hash.
  • livepeer_orch_reward_gas_used: This metric represents the gas used in each reward transaction. It includes the id label representing the transaction hash.
  • livepeer_orch_reward_gas_price: This metric represents the gas price in Wei used for executing the reward transaction. It includes the id label representing the transaction hash.
  • livepeer_orch_reward_gas_cost: This metric represents the gas cost of each reward transaction in Gwei. It includes the id label representing the transaction hash.
  • livepeer_orch_reward_block_number: This metric denotes the block number in which each reward transaction was included. It includes the id label representing the transaction hash.
  • livepeer_orch_reward_block_time: This metric represents the block time of the block in which each reward transaction was included. It includes the id label representing the transaction hash.
  • livepeer_orch_reward_round: This metric represents the Livepeer protocol round in which each reward transaction was executed. It includes the id label representing the transaction hash.

Note

Due to an upstream bug, the livepeer_orch_reward_gas_used metric currently shows the gas limit instead (see this upstream issue). This will be fixed once the upstream issue is resolved.

orch_score_exporter

The orch_score_exporter fetches metrics about the Livepeer orchestrator's score from the Livepeer Score API endpoint. These metrics provide insights into the performance of the orchestrator. They include:

Gauge metrics:

  • livepeer_orch_price_per_pixel: This metric represents the price per pixel in Wei.

GaugeVec metrics:

  • livepeer_orch_success_rate: This metric represents the success rate per region. It can be used to monitor the reliability of the orchestrator in different areas. It includes the region label.
  • livepeer_orch_round_trip_score: This metric represents the round trip score per region. It can measure the latency of the orchestrator in different areas. It includes the region label.
  • livepeer_orch_total_score: This metric represents the total score per region. It can be used to evaluate the orchestrator's overall performance in different areas. It includes the region label.

orch_test_streams_exporter

The orch_test_streams_exporter fetches metrics about the Livepeer orchestrator's test streams from the https://leaderboard-serverless.vercel.app/api/raw_stats API endpoint. These metrics provide insights into the performance of the orchestrator's test streams in different regions. They include:

GaugeVec metrics:

  • livepeer_orch_test_stream_success_rate: This metric represents the success rate per region for test streams. It can monitor the reliability of the orchestrator in different regions. It includes the region and orchestrator labels.
  • livepeer_orch_test_stream_upload_time: This metric represents the two-segment upload time per region for test streams. It measures the upload speed of the orchestrator in different regions. It includes the region and orchestrator labels.
  • livepeer_orch_test_stream_download_time: This metric represents the two-segment download time per region for test streams. It measures the download speed of the orchestrator in different regions. It includes the region and orchestrator labels.
  • livepeer_orch_test_stream_transcode_time: This metric represents the two-segment transcode time per region for test stream. It measures the transcoding speed of the orchestrator in different regions. It includes the region and orchestrator labels.
  • livepeer_orch_test_stream_round_trip_time: This metric represents the two-segment round trip time per region for test streams. It measures the overall latency of the orchestrator in different regions. It includes the region and orchestrator labels.

orch_tickets_exporter

The orch_tickets_exporter fetches and exposes winning ticket transaction information from the Livepeer subgraph endpoint. These metrics provide insights into the orchestrator's winning tickets. They include:

Gauge metrics:

  • livepeer_orch_day_fees: This metric represents the ETH fees won by the orchestrator in the last 24 hours.
  • livepeer_orch_week_fees: This metric represents the ETH fees won by the orchestrator in the last 7 days.
  • livepeer_orch_thirty_day_fees: This metric represents the ETH fees won by the orchestrator in the last 30 days.
  • livepeer_orch_ninety_day_fees: This metric represents the ETH fees won by the orchestrator in the last 90 days.
  • livepeer_orch_year_fees: This metric represents the ETH fees won by the orchestrator in the last 365 days.
  • livepeer_orch_total_fees: This metric represents the total ETH fees won by the orchestrator.
  • livepeer_orch_tickets_day_gas_cost: This metric represents the gas cost of the winning ticket transactions in the last 24 hours.
  • livepeer_orch_tickets_week_gas_cost: This metric represents the gas cost of the winning ticket transactions in the last 7 days.
  • livepeer_orch_tickets_thirty_day_gas_cost: This metric represents the gas cost of the winning ticket transactions in the last 30 days.
  • livepeer_orch_tickets_ninety_day_gas_cost: This metric represents the gas cost of the winning ticket transactions in the last 90 days.
  • livepeer_orch_tickets_year_gas_cost: This metric represents the gas cost of the winning ticket transactions in the last 365 days.
  • livepeer_orch_tickets_total_gas_cost: This metric represents the total gas cost of the winning ticket transactions.

GaugeVec metrics:

  • livepeer_orch_winning_ticket_amount: This metric represents the ETH fees won by each winning orchestrator ticket. It includes the id label representing the transaction hash of each ticket.
  • livepeer_orch_winning_ticket_gas_used: This metric represents the gas used in redeeming each winning ticket. It includes the id label representing the transaction hash of each ticket.
  • livepeer_orch_winning_ticket_gas_price: This metric represents the gas price in Wei used in redeeming each winning ticket. It includes the id label representing the transaction hash of each ticket.
  • livepeer_orch_winning_ticket_gas_cost: This metric represents the gas cost in Gwei of redeeming each winning ticket. It includes the id label representing the transaction hash of each ticket.
  • livepeer_orch_winning_ticket_block_number: This metric represents the block number for each winning ticket. It includes the id label representing the transaction hash of each ticket.
  • livepeer_orch_winning_ticket_block_time: This metric represents the block time for each winning ticket. It includes the id label representing the transaction hash of each ticket.
  • livepeer_orch_winning_ticket_round: This metric represents the round in which each winning ticket was won. It includes the id label representing the transaction hash of each ticket.

Note

Due to an upstream bug the livepeer_orch_winning_ticket_gas_used metric currently shows the gas limit instead (see this upstream issue). This will be fixed once the upstream issue is resolved.

Contributing

Feel free to open an issue if you have ideas on how to make this repository better or if you want to report a bug! All contributions are welcome. 🚀 Please consult the contribution guidelines for more information.

Shout-out

🚀 Stronk.rocks: Special thanks to @stonk-dev for pointing me to the needed API endpoints needed to implement this exporter.

livepeer-exporter's People

Contributors

dependabot[bot] avatar github-actions[bot] avatar rickstaa avatar

Watchers

avatar

livepeer-exporter's Issues

Replace stronk API calls with calls to TheGraph

Is your feature request related to a problem? Please describe.

@stronk-dev brought https://api.thegraph.com/subgraphs/name/livepeer/arbitrum-one/graphql to my attention. This endpoint can fetch most of the information I currently fetch from https://stronk.rocks.

Rewards call example

{
  rewardEvents (where: {delegate: "0x9d61ae5875e89036fbf6059f3116d01a22ace3c8"}){
    id
    rewardTokens
    delegate {
      id
    }
  }
}

Describe the solution you'd like

I want to replace the https://stronk.rocks calls with https://api.thegraph.com/subgraphs/name/livepeer/arbitrum-one/graphql calls to ellivate the https://stronk.rocks service.

Describe alternatives you've considered

No response

Additional context

TODOs

  • Migrate orch_rewards_exporter.
  • Migrate orch_tickets_exporter.
  • Migrate orch_delegators_exporter.

Add orchestrator reward call ratio

Is your feature request related to a problem? Please describe.

It would be nice to add the reward call ratio as displayed on the livepeer-explorer.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

Migrate several metrics into the `go-livepeer` binary

Is your feature request related to a problem? Please describe.

Some metrics might already retrieved inside the go-livepeer binary. As a result, exposing them inside the go-livepeer binary is more efficient.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

Metrics that can be migrated

Note

Please feel free to comment below if you find metrics that can be migrated. I will then create a pull request at go-livepeer and deprecate them from the exporter.

Add orchestrator claimed rewards exporter

Is your feature request related to a problem? Please describe.

Introducing an exporter that fetches and exposes the LivePeer rewards claimed by the orchestrator would be beneficial.

Describe the solution you'd like

I examined the https://github.com/stronk-dev/LivepeerEvents/wiki/API-Call:-getAllRewardEvents endpoint for this purpose. However, I'm still looking for an endpoint specifically tailored to include only the rewards claimed by the orchestrator. This optimization would reduce fetch size and thereby decrease network traffic.

Describe alternatives you've considered

Alternatively, we can only fetch the rewards once every 6 hours.

Additional context

No response

Gas used metrics are incorrect

Describe the bug

As pointed out by @stronk-dev the livepeer_orch_reward_gas_used and livepeer_orch_winning_ticket_gas_used metrics return the gas limit instead of the used gas (see #67 (comment)). This is caused by this upstream bug.

Reproduction steps

No response

Expected behaviour

No response

Screenshots / Live demo link

No response

System information

No response

Additional context

No response

Add orchestrator winning tickets exporter

Is your feature request related to a problem? Please describe.

Introducing an exporter that fetches and exposes the LivePeer tickets won by the orchestrator would be beneficial.

Describe the solution you'd like

I examined the https://github.com/stronk-dev/LivepeerEvents/wiki/API-Call:-getAllRedeemTicketEvents endpoint for this purpose. However, I'm still looking for an endpoint specifically tailored to include only the tickets won by the orchestrator. This optimization would reduce fetch size and, thereby, network traffic.

Describe alternatives you've considered

Alternatively, we can only fetch the tickets once every 6 hours.

Additional context

No response

Replace livepeer explorer API with a TheGraph call

Describe the bug

The Livepeer explorer API endpoints appear quite dynamic, making it a top priority to transition it into a thegraph call:

{
  transcoder (id:"0x5bdeedca9c6346b0ce6b17ffa8227a4dace37039"){
    delegator{
      bondedAmount
      withdrawnFees
    	lastClaimRound{
        id
      }
      startRound
    }
    totalStake
    lastRewardRound{
      id
    }
    activationRound
    active
    feeShare
    pools{
      rewardTokens
    }
    rewardCut
    lastRewardRound{
      id
    }
    ninetyDayVolumeETH
    thirtyDayVolumeETH
    totalVolumeETH
    
  }
  protocol(id: "0"){
    currentRound{
      id
    }
  }
}

Reproduction steps

  1. Checkout commit 22d96d1.
  2. See that the orch_info_exporter metrics are broken.
  3. Go to https://explorer.livepeer.org/, check the orchestrating.js API, and see that it has changed.

Expected behaviour

No response

Screenshots / Live demo link

No response

System information

  • Run method: docker
  • OS: Ubuntu 22.04
  • Exporter version: v2.1.4

Additional context

No response

`livepeer_orch_total_volume_eth` not updating

Describe the bug

It seems that the livepeer_orch_total_volume_eth metric is not updating correctly.

Reproduction steps

  1. Go to https://dashboards.transcode.ninja/public-dashboards/612ce9347bc44e1885e6417b145f4093?orgId=1&refresh=30s
  2. Check the pageProps.account.transcoder.totalVolumeETH value at the Livepeer endpoint.
  3. See that my orchestrator already won 0.012 ETH, but the exporter still exports 0 eth.

Expected behaviour

No response

Screenshots / Live demo link

No response

System information

  • Run method: docker
  • OS: Ubuntu 20.04
  • Version: 2.4.1

Additional context

No response

`livepeer_orch_delegator_bonded_amount` doe not include pending stake

Describe the bug

I just noticed that the livepeer_orch_delegator_bonded_amount parameter does not include the pending stake accumulated due to network inflation. It would also make sense to offer users the ability to show the total reward (i.e. bonded + pending).

Reproduction steps

  1. Go to https://dashboards.transcode.ninja/public-dashboards/612ce9347bc44e1885e6417b145f4093?orgId=1&refresh=30s.
  2. Check out the delegators panel.
  3. See the summed rewards don't add up to the amount shown on the orchestrator transcoder page.

Expected behaviour

No response

Screenshots / Live demo link

No response

System information

  • Run method: docker
  • OS: Linux Ubuntu 22.04
  • Exporter version: 2.4.1

Additional context

No response

Add general protocol information to the exporter

Is your feature request related to a problem? Please describe.

It would be nice to show general LivePeer protocol information to the exporter, similar to the data displayed on the https://explorer.livepeer.org/ page.

image

TODOs

  • Add daily fees paid (i.e. livepeer_exporter_protocol_fees_paid).
  • Add daily participation rate (i.e. livepeer_exporter_protocol_participation_rate).
  • Add daily inflation rate (i.e. livepeer_exporter_protocol_estimated usage).
  • Add daily delegators count (i.e. livepeer_exporter_protocol_delegators).
  • Add daily orchestrators count (i.e. livepeer_exporter_protocol_orchestrators).
  • Current round progress (e.g. livepeer_exporter_protocol_current_round_blocks_remaining, livepeer_exporter_protocol_current_round_time_remaining, livepeer_exporter_protocol_current_round_progress).
  • Current round fees (i.e. livepeer_exporter_protocol_current_round_fees).
  • Current round rewards (i.e. livepeer_exporter_protocol_current_round_rewards).

Describe the solution you'd like

We can fetch this information from the following endpoints:

Describe alternatives you've considered

No response

Additional context

No response

Delegators not removed when they undelegate

Describe the bug

I just noticed a minor bug that causes delegators already undelegated to be still returned by livepeer_orch_delegator_bonded_amount.

Reproduction steps

  1. Ensure the exporter is started as explained in the README.
  2. Ensure you delegate and undelegate LPT to your orchestrator in two rounds.
  3. Go to the Grafana Explore tab.
  4. Checkout the livepeer_orch_delegator_bonded_amount metric.
  5. See that the exporter still returns the accounts already undelegated.

Expected behaviour

These undelegated accounts should not be returned.

Screenshots / Live demo link

No response

System information

  • Run method: Docker
  • OS: Linux
  • Exporter version: 2.8.1

Additional context

This possible is an easy bug to fix since this data is not returned by the Livepeer Subgraph.

livepeer_orch_thirty_day_reward_claim_ratio metric is broken

Describe the bug

It looks like the livepeer_orch_thirty_day_reward_claim_ratio metric is broken.

image

image

Reproduction steps

  1. Go to https://dashboards.transcode.ninja/public-dashboards/612ce9347bc44e1885e6417b145f4093?orgId=1&refresh=30s.
  2. Check the value on the Call Ratio panel.
  3. Go to https://explorer.livepeer.org/accounts/0x5bdeedca9c6346b0ce6b17ffa8227a4dace37039/orchestrating
  4. See that the call ratio is 30/30.

Expected behaviour

The call ratio given by the variable should be 100%.

Screenshots / Live demo link

No response

System information

  • Run method: docker
  • OS: ubuntu 22.04
  • Exporter version: v2.8.1

Additional context

No response

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.