-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add monitoring stack #5
base: main
Are you sure you want to change the base?
Conversation
I tested the setup_monitoring.sh and it failed because my laptop didn't had kustomize installed. |
I would like to keep the requirements to a minimal level, without requiring development tools. We shouldn't forget that the audience are not developers. |
so instead of kustomize, kubectl apply -f < the directory >? |
@smiyc I did some minor changes and removed the needed of kustomize, can you check again please! :D |
@sxd the monitoring stack is set up correctly without kustomize. |
@smiyc it should be in the playlists section, can you check please? :D |
nope |
@smiyc will create a fresh environment to test, and check, but in the meantime, can you check the status of the grafana operator ? looking for errors or something. |
the operator wants to download the dashboard from my external IP address...
a ...after connecting via hotspot, the dashboard was downloaded... |
4f37be5
to
997b8d5
Compare
Every cluster now has the podMonitor enabled and the script scripts/setup_monitoring.sh was created to deploy Prometheus Operator and Grafana Operator, using these operators we create: * Prometheus instance * Grafana Deployment * Grafana Datasource (connecting to Prometheus instance) * Grafana Dashboard (from the project cloudnative-pg/grafana-dashboard) After the cluster are updated the Grafana dashboard can be accessed redirecting the 3000 port of the Grafana deployment (namespace grafana) on any of the two kind clusters. The dashboard is loaded from the URL of the json file in the repository, this means that if the content is changed also the dashboard will be updated. Signed-off-by: Jonathan Gonzalez V. <[email protected]>
Signed-off-by: Jonathan Gonzalez V. <[email protected]>
Signed-off-by: Gabriele Bartolini <[email protected]>
Signed-off-by: Gabriele Bartolini <[email protected]>
Signed-off-by: Gabriele Bartolini <[email protected]>
Signed-off-by: Gabriele Bartolini <[email protected]>
Signed-off-by: Gabriele Bartolini <[email protected]>
Signed-off-by: Gabriele Bartolini <[email protected]>
Signed-off-by: Gabriele Bartolini <[email protected]>
e0bb90c
to
8e3d2de
Compare
@sxd can you please review this? please do not merge as we need to add Leonardo as co author. |
@gbartolini on it!! will modify the commit message too ;) BTW nice changes! |
Every cluster now has the podMonitor enabled and the script scripts/setup_monitoring.sh was created to deploy Prometheus Operator and Grafana Operator, using these operators we create:
After the cluster are updated the Grafana dashboard can be accessed redirecting the 3000 port of the Grafana deployment (namespace grafana) on any of the two kind clusters.
The dashboard is loaded from the URL of the json file in the repository, this means that if the content is changed also the dashboard will be updated.