oslabs-beta / oslabs-beta/TrailGuide
Successful/clean data pipeline (ETL) to response data
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 28
- Forks
- 0
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Problem
- check options via cloudwatch/cloudtrail on getting clean response data
- check other services (ETL) options in aws
Solution
- do more research in aws while consider time and cost
Additional information
No response
👨👧👦 Contributing
- 🙋♂️ Yes, I'd love to make a PR to implement this feature!
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.
Research direction
No source file, test, or entry point is named. Start by reviewing the existing CloudTrail response-data flow, then compare CloudWatch, CloudTrail, and AWS ETL options with time and cost in mind. Done requires a decided approach for producing clean response data, but the issue does not define acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, data-engineering, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100