Monitor and Analyze Cloud Resource Usage
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
- Tech stack
- python
- Domain
- cloud, observability-sre
Research direction
The issue does not name any files, tests, cloud provider, or monitoring entry point. Start by inventorying how the toolkit currently uses cloud resources and identify the project’s supported monitoring scope; done should include usage, performance, and cost tracking plus documented optimization insights.
Written by the indexing model from the issue text.
Description
Implement monitoring and analytics to track the usage, performance, and cost of cloud resources used by the toolkit. Use insights from monitoring to optimize cloud resource utilization.
- Dominant language
- Jupyter Notebook
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor 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 thomasthaddeus/DataAnalysisToolkit
-
Data-Import Development
thomasthaddeus/DataAnalysisToolkit#209 · 1 assignee ·
-
documentation Research
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Plugin Architecture Quality Assurance
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Maintenance Plugin Architecture
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Deployment Plugin Architecture
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in thomasthaddeus/DataAnalysisToolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
Feature needs-triage pulumi/registry
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100