Midburn / Midburn/midburn-devops
monitoring for AWS resources
Open
Nobody has claimed this yet.
AWS
monitoring
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Setup monitoring on AWS with grafana
EC2 and ALB would be the best two to start with.
http://docs.grafana.org/features/datasources/cloudwatch/
https://github.com/monitoringartist/grafana-aws-cloudwatch-dashboards
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the linked Grafana CloudWatch data-source documentation and the monitoringartist Grafana AWS CloudWatch dashboards repository. Determine the project’s AWS and Grafana entry points, then define monitoring coverage for EC2 and ALB. Done means both resource types are represented in Grafana with the expected metrics and dashboards.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, grafana
- Domain
- cloud, devops, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100