You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To bolster observability and performance monitoring within the Livepeer AI network, we want to develop a Grafana Dashboard focused on Orchestrator Metrics. This dashboard will deliver vital insights into the AI-job operations managed by Orchestrators, empowering them with approximate health metrics of their servers. By offering a comparative analysis of their operations against others in the network, orchestrators will gain the tools needed to optimize their nodes and secure more work opportunities. 🚀
We invite the community to contribute to this essential initiative, which will significantly enhance orchestrator operations and visibility. The implementation of this dashboard is key to monitoring and optimizing AI job requests and orchestrator performance, ensuring the AI subnet operates at peak efficiency. 🔥
Experience with Prometheus for metrics collection.
Bounty Requirements
Several orchestrator-specific metrics have been added to the ai-video branch through this pull request. Leveraging these metrics, the bounty hunter is expected to:
Implementation: Develop a user-friendly Grafana Dashboard that is easy to set up and tailored for Orchestrators within the network. Following create a pull request to the Livepeer grafana dashboards repository.
Functionality: The dashboard should showcase essential metrics such as number of requests per model and pipeline, price per unit paid per request, request latency score, error rates, estimated inference earnings, total tickets received, winning tickets, and other critical data points.
Scope Exclusions
Scope Exclusions
This bounty does NOT cover the addition of new metrics like livepeer_current_ai_sessions_total. These additional metrics can be considered in a future bounty.
Implementation Tips
To understand how to work with Orchestrator metrics, you can refer to a recent pull request that is similar and deals with metrics for Gateway operators.
Leverage Existing Metrics: Review existing metrics related to AI requests on the Gateway side, which are already implemented on the Cloud Gateway Dashboard. This will provide an initial template for a starting point.
Utilize Documentation: Check out livepeer forum for basic instructions on how to get started setting up the prometheus and grafana.
How to Apply
Express Your Interest: Comment on this issue to indicate your interest and explain why you're the ideal candidate for the task.
Wait for Review: Our team will review expressions of interest and select the best candidate.
Get Assigned: If selected, we'll assign the GitHub issue to you.
Start Working: Dive into your task! If you need assistance or guidance, comment on the issue or join the discussions in the #developer-lounge channel on our Discord server.
Submit Your Work: Create a pull request in the relevant repository and request a review.
Notify Us: Comment on this GitHub issue when your pull request is ready for review.
Receive Your Bounty: We'll arrange the bounty payment once your pull request is approved.
Gain Recognition: Your valuable contributions will be showcased in our project's changelog.
Thank you for your interest in contributing to our project! 💛
Warning
Please wait for the issue to be assigned to you before starting work. To prevent duplication of effort, submissions for unassigned issues will not be accepted.
The text was updated successfully, but these errors were encountered:
Thank you for your interest in contributing to our open-source community ❤️🔥! Unfortunately, this bounty is actually part two of a previous task, which you can find here: #49. It was created to break the larger task into smaller parts, and as such, it has already been assigned to someone working on the initial bounty.
You can check out the implementation progress here: link.
We regularly post new bounties, so I'm confident there will be more opportunities for you to contribute soon. Keep an eye out, and we hope to see you involved in future projects 🚀!
Overview
To bolster observability and performance monitoring within the Livepeer
AI network
, we want to develop a Grafana Dashboard focused onOrchestrator
Metrics. This dashboard will deliver vital insights into the AI-job operations managed by Orchestrators, empowering them with approximate health metrics of their servers. By offering a comparative analysis of their operations against others in the network, orchestrators will gain the tools needed to optimize their nodes and secure more work opportunities. 🚀We invite the community to contribute to this essential initiative, which will significantly enhance orchestrator operations and visibility. The implementation of this dashboard is key to monitoring and optimizing AI job requests and orchestrator performance, ensuring the AI subnet operates at peak efficiency. 🔥
Required Skillset
Bounty Requirements
Several orchestrator-specific metrics have been added to the
ai-video
branch through this pull request. Leveraging these metrics, the bounty hunter is expected to:Orchestrators
within the network. Following create a pull request to the Livepeer grafana dashboards repository.number of requests per model and pipeline
,price per unit paid per request
,request latency score
,error rates
,estimated inference earnings
,total tickets received
,winning tickets
, and other critical data points.Scope Exclusions
Scope Exclusions
livepeer_current_ai_sessions_total
. These additional metrics can be considered in a future bounty.Implementation Tips
To understand how to work with
Orchestrator
metrics, you can refer to a recent pull request that is similar and deals with metrics for Gateway operators.Pull Request #3087
Additionally, make sure to:
prometheus
andgrafana
.How to Apply
#developer-lounge
channel on our Discord server.Thank you for your interest in contributing to our project! 💛
Warning
Please wait for the issue to be assigned to you before starting work. To prevent duplication of effort, submissions for unassigned issues will not be accepted.
The text was updated successfully, but these errors were encountered: