You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a) Installing Prometheus and Grafana on the EKS cluster:
Simplifies configuration.
Monitoring becomes inaccessible if the cluster goes down.
b) Setting up Prometheus and Grafana on external infrastructure from the EKS cluster:
Medium complexity in implementation.
Monitoring remains accessible if the cluster fails.
c) Deploying Prometheus with Thanos on the EKS cluster and Grafana externally:
Thanos becomes inaccessible if the cluster fails.
d) Deploying Prometheus with a Thanos sidecar within the EKS cluster, while positioning Thanos Store, Query components, and Grafana outside the cluster:
Ensures monitoring access even if the cluster fails.
Requires a more complex setup.
Which option is considered the best practice for EKS cluster monitoring?
a) Installing Prometheus and Grafana on the EKS cluster
0%
b) Setting up Prometheus and Grafana on external infrastructure from the EKS cluster
0%
c) Deploying Prometheus with Thanos on the EKS cluster and Grafana externally
0%
d) DeployPrometheus with a Thanossidecar within the EKS cluster, while positioning ThanosStore,Query,Grafana outside the cluster
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
a) Installing Prometheus and Grafana on the EKS cluster:
b) Setting up Prometheus and Grafana on external infrastructure from the EKS cluster:
c) Deploying Prometheus with Thanos on the EKS cluster and Grafana externally:
d) Deploying Prometheus with a Thanos sidecar within the EKS cluster, while positioning Thanos Store, Query components, and Grafana outside the cluster:
0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions