grafana-aws-cloudwatch-dashboards
cluster-monitoring
Our great sponsors
| grafana-aws-cloudwatch-dashboards | cluster-monitoring | |
|---|---|---|
| 2 | 4 | |
| 1,968 | 731 | |
| 1.0% | - | |
| 5.9 | 1.7 | |
| 30 days ago | about 2 months ago | |
| Jsonnet | Jsonnet | |
| GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
grafana-aws-cloudwatch-dashboards
-
Importing dashboard with API
I've been using the "guide" here: https://github.com/monitoringartist/grafana-aws-cloudwatch-dashboards
-
Monitoring and logging with Amazon Managed Workflows for Apache Airflow
Creation of dashboards in Grafana dashboards is outside the scope of this post, but you should have everything you need to get going now. I did find and spend some time exploring this great resource that will probably be a great help if you want to go down this path.
cluster-monitoring
-
Having issues modifying Grafana deployment using kube-prometheus
I've grabbed the Prometheus stack from carlosedp/clustermonitoring and was able to get that deployed into my cluster. That stack is fairly dated and is pulling some pretty old versions of some of the containers. I decided to see if I could get the stack upgraded to the latest version of the containers as a learning exercise, but I'm running into an issue upgrading kube-prometheus to release-0.10.
-
Kubernetes Cluster Monitoring
If you are running on arm this is a nice project to try. https://github.com/carlosedp/cluster-monitoring
-
Recommended setup for a Kubernetes cluster
Prometheus stack via Carlos Eduardo's phenomenal clustermonitoring repo, modified to account for some differences in my setup (NFS-based PVs, MetalLB already set up, ingress annotations)
-
How Do I Stop My Cluster From Refusing Connections
The main thing that jumped out to me was this hard coded IP: https://github.com/carlosedp/cluster-monitoring/blob/a136833aaf364a8e76809a9dca789bb59e070677/manifests/ingress-grafana.yaml#L8
What are some alternatives?
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
cloudprober - [Moved to cloudprober/cloudprober] An active monitoring software to detect failures before your customers do.
k3s - Lightweight Kubernetes
Netdata - The open-source observability platform everyone needs
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
netdata - Real-time performance monitoring, done right! https://www.netdata.cloud [Moved to: https://github.com/netdata/netdata]
robusta - Kubernetes observability and automation, with an awesome Prometheus integration
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes [Moved to: https://github.com/prometheus-operator/kube-prometheus]
cw - The best way to tail AWS CloudWatch Logs from your terminal
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services