Proposal: Enhanced User Logging System on Akash Console #727
Replies: 7 comments 10 replies
-
Hey @HoomanDgtl (Piyush and Chai), Thanks very much for initiating this and for coming up with the POC and presenting it to the core team. To echo what you said above, not being able to capture, retain and query past logs easily is a very acute painpoint for our customers and solving it is one of 3-4 top level initiatives on the Console Roadmap (alongside CC payments, Alerting/ Notifications and better/ easier workflows for non-container native developers). To recap our discussion (between the core team and your team):
With those things in mind, the recommendation from the core team is to:
I'll note that the above proposed solution does require that the user be familiar with external logging solutions, how to set them up and how to use them to query logs so this would not be for less technical users (like those who use vercel) - but for now I think this is a good solution to at least address the logging problem for users who understand infrastructure (which I would argue is a vast majority of akash users today). Over time we can look at offering a more seamless experience where the user does not need to configure anything and just pays for a service in Console to "take care of logging" (whether that involves storing logs on akash providers or some other decentralized storage provider like StorJ or Filecoin or to a centralized logging service. Thanks again for working on this critical problem and we look forward to the updated "Log Forwarding" proposal from you |
Beta Was this translation helpful? Give feedback.
-
Thank you, @anilmurty and team, for your constructive feedback and suggestions. We will follow up with an updated proposal within this week. Best regards, |
Beta Was this translation helpful? Give feedback.
-
The proposal is scheduled to go live onchain tomorrow. |
Beta Was this translation helpful? Give feedback.
-
The proposal is live onchain: Click here |
Beta Was this translation helpful? Give feedback.
-
Hello 👋🏻 thank you for your proposal. |
Beta Was this translation helpful? Give feedback.
-
Hi @HoomanDgtl, I completely agree that this would be a valuable addition, even as a temporary solution until a protocol-level implementation can be achieved. I have a couple of questions for clarification (apologies for raising these post-proposal): Open Source Code: Will the resulting code be open-sourced and hosted on the Akash Network GitHub? I didn’t see this explicitly mentioned in the proposal, but I believe it’s an important consideration since the community pool is funding the work. Open-sourcing would not only align with the ethos of the ecosystem but also allow users to extend the solution to other logging providers in the future. Work Estimate: The estimated 780 hours (~20 weeks) for completion feels quite high at first glance. While I understand this likely reflects the complexity of the task, could you elaborate on the specific challenges that account for this level of effort? For example, does the scope include protocol-level changes to ensure reliable, non-application-specific log access, or are there other factors driving the estimate? Looking forward to your thoughts and thanks again for pushing this forward! |
Beta Was this translation helpful? Give feedback.
-
Vector is already doing all this. vector It would be enough to install it as a service. At most, create a front UI. |
Beta Was this translation helpful? Give feedback.
-
Proposal: Log Forwarding Integration for the Akash Network: Empowering User-Controlled Logging Solutions
Introduction
This proposal represents a strategic pivot in our approach to implementing logging solutions for the Akash Network. Following in-depth discussions with the Akash core team, we have refined our strategy to better align with the network's principles of decentralization and user needs while maintaining simplicity and effectiveness.
Initially, we proposed developing a self-hosted logging infrastructure using Grafana, Prometheus, and Loki. However, discussions with the core team highlighted the following key insights:
Based on these insights, we revised our approach to focus on integrating robust log forwarding capabilities, allowing users to utilize their preferred logging solutions while maintaining full control over their data and costs.
Problem Statement
The Akash Network console currently lacks a persistent logging system, leading to significant challenges:
Proposed Solution
We propose integrating comprehensive log forwarding capabilities into the Akash console to:
Implementation Details
Console Integration
Settings Page Enhancement:
SDL Builder Integration:
Technical Implementation
Logging Sidecar Service:
Supported Logging Destinations (Initial Phase):
(Expand support to additional platforms based on user feedback.)
Implementation Timeline (2-3 Months)
Phase 1: Frontend Development
Phase 2: Backend Development
Phase 3: Testing and Documentation
Expected Outcomes
This revised logging integration approach will provide:
This solution aligns with Akash Network's principles of decentralization and user empowerment while providing immediate value to the community.
Budget Estimate
The following budget reflects the comprehensive scope of work required:
Total Hours: 780
Hourly Rate: $100
Total Budget: $78k
This budget ensures a professional-grade implementation of log forwarding integration, addressing user pain points while aligning with Akash Network's values.
Governance Timeline
Link to POC Video: click here
Previous Prop & plan (just for record): click here
Thank you for considering this proposal. We welcome your feedback and community support on our updated plan. If you have any questions, please feel free to ask below.
Thank you
Beta Was this translation helpful? Give feedback.
All reactions