View insights for how the many-framework is used in production
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api, observability
Research direction
Start by reviewing the many-framework network API and how the Manifest ledger and kvstore are used in production. Resolve which metrics would inform fees and network rates and where they should be presented. Done means the selected metrics are available through the production network API, can target the Manifest ledger, and can be demonstrated in production.
Written by the indexing model from the issue text.
Description
Description: This story is to add metrics to production for the many-framework so we can gather how the current ledger (and kvstore once in prod) is being used. The data generated can help inform decisions about fees and rates for network usage. With this story combined with #20 we'll be in a good place to start making decisions on fees and rates as a company. These should be blocking for smart contract work.
Story ROI:
Business Objective: This will provide insights for how our framework is used by customers and help with determining the fees and rates for network usage which will be our main revenue source. This story will also be useful for smart contract work that is to come.
As TLI, I want to view insights for how the many-framework (ledger, kvstore) is used in production so that I stay informed.
- Should make metrics available from the network API (many-framework) in production.
- Should be able to target the Manifest ledger in production.
- [DISCOVERY] Should present the metrics: TBD.
- Should be able to be demoed in the prod network.
Questions:
- What metrics should be included to be helpful for knowing how the ledger (and kvstore once in prod) are being used that informs a rate and network fee structure?
- Where should these metrics present themselves?
Tasks:
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from liftedinit/roadmap
-
gwen ui
Difficulty 3/5 1-2 days Newbie friendliness 35/100
liftedinit/roadmap#115 ·
-
gwen ui
Difficulty 3/5 1-2 days Newbie friendliness 35/100
liftedinit/roadmap#114 ·
-
Gwen - ContactsOpenbackend gwen story ui
Difficulty 4/5 3-5 days Newbie friendliness 35/100
liftedinit/roadmap#113 ·
-
gwen ui
Difficulty 4/5 3-5 days Newbie friendliness 35/100
liftedinit/roadmap#111 ·
-
gwen ui
Difficulty 4/5 3-5 days Newbie friendliness 35/100
liftedinit/roadmap#108 ·
All issues in liftedinit/roadmap
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FuRongJun-1999/dsh-memory#170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
[BUG] Re-subscribing the Mono returned by listTools/listResources/listResourceTemplates/listPrompts/listRoots duplicates the resultsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/java-sdk#1174 · 1 reaction ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NanmiCoder/cc-haha#1533 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
maxrave-dev/SimpMusic#2649 ·
Maintainers usually reply within 2 days