"helm install grafana stable/grafana" is depricated. you should use : helm install grafana grafana/grafana" instead. otherwise great video. thank you for your help!
Dear Author, thank you for this amazing video. Also, I want to point out one error that you have made at 15:54 pod/prometheus-alertmanager READY 2/2 (Does not mean it have two pods or the count of pod is 2) (It means the running pod is having two containers and both are running.) or we can say that (number of running containers/Total number of containers)
Thank you for the informative video! I have a quick question: What is the recommended approach for retrieving Prometheus data from a multi-node cluster? Should we deploy a DaemonSet or sidecar, or is there another preferred method?
great videos! can you please tell which chart should I use? - (kube-prometheus-stack): include prometheus operator which I believe is more powerful and easy to manage - or (prometheus). currently running on our EKS cluster. My concern is about future: - We will be using this as centeral monitoring point for for both production and staging env. So I am thinking which chart will be good for ease of management and scalability? Need to mention, we are deploying this with terraform helm provider. thanks!
Kube prometheus stack will be easier one to deploy and use, you will have to go through the details of their roadmap plan as your future management of the system will be based on that.
Thanks for the great video. I have one doubt, you have added Prometheus as source in Grafana UI, what happens if the grafana pod is recreated, do we need to add it again after pod recreation? or can we give a source to the Grafana directly in its helm chart ?
I’ve created a server on which I’ve configured Prometheus and Grafana. On prometheus I’m monitoring my 10 VMs. I also want to monitor my AKS cluster and 2 Microk8s cluster on same Prometheus. How can I achieve my goal?
Can you please help me with how to do it on multiple AWS accounts without VPC peering? I need to get metrics from private IP subnets using any exporter and IAM role ... Please help
Hey, I want the mtrics of my pods which i have created (bascially deployments), so where is the prometheus configuration file, so that i can alter it according to me?
I am unable to access the Prometheus and Grafana dashboards from my browser. However, when I run a curl command using :, I receive a response within the cluster. can you suggest me what can be the issue?
as it seems to keep the history it should have to use Persistent volume. since we haven't configured it does it mean it will wipe out the history on the next restart? if not then how it is possible where it is keeping the data.
I checked they are using PV and PVC using hostpath, which means the data would be stored on the host. Once the pods are recreated they will have the data back from there. I hope this answers your query.
Hi, After exposing the grafana clusterIP service as a Nodeport, I get ERR_CONNECTION_TIMED_OUT when I type x.x.x.x:32578 in my browser. I run a 3 node k8s cluster with 1 controlplane and 2 worker nodes. Can you please help?
I have installed minikube with docker driver on Ubuntu 20.04 and instlled helm and install Prometheus based on your video but iam not able to accessible from browser getting site can't be reached
I have configured the same but unable the see the data for CPU, Memory and IO same like your dashboard I see the N/A. Could you please share the steps to fix this
My dear friend.. where is configured node_expoter in Prometheus.yml file. With port 9100 and .how can you recived metrics without configured of node_exporter in prometheus.yl file...... please reply
I installed Prometheus and grafana as per this video using helm on Azure Ubuntu VM And exposed the svc using nodeport but not able to access the server Please help
Hello can you explain why I'm getting this error when installing prometheus? helm install prometheus-release prometheus-community/prometheus Error: template: prometheus/templates/NOTES.txt:86:46: executing "prometheus/templates/NOTES.txt" at : error calling index: index of untyped nil
i check logs pod [root@k8smaster2 ~]# kubectl logs prometheus-server-7d57c9697f-hqngs Defaulted container "prometheus-server-configmap-reload" out of: prometheus-server-configmap-reload, prometheus-server 2022/06/29 14:18:46 Watching directory: "/etc/config" please help to check.
Hi, I was installing Prometheus. After "helm install prometheus prometheus-community/prometheus", I noticed that alertmanager and prometheus-server pods are in Pending state for more than 30 minutes. Appreciate any help. I have tried it twice - appreciate some help. Thx.
This is what I get from describing the pod towards the end. Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 18m default-scheduler 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims. Warning FailedScheduling 18m default-scheduler 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims. Warning FailedScheduling 13m default-scheduler 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims. arjun@k8s-controller-01-hp:~$
Looks like there are two pvc's but no pv's. arjun@k8s-controller-01-hp:~$ kubectl get pv No resources found arjun@k8s-controller-01-hp:~$ kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE my-prometheus-alertmanager Pending 45m my-prometheus-server Pending 45m arjun@k8s-controller-01-hp:~$
There is some issue creating the persistent volume. I would suggest you to clean the release and delete the PV, PVC if anything there manually. Restart the docker service and then try again.
I've been spending days trying to get to this point and your tutorial is the one that finally got me there. Thank you.
That is really great to hear
Hi this is Ravi Kumar I am also same way but when trying to access from browser getting site can't be reached
thank you brother. as a new comer to be Devops engineer, I really appreciate this video.
You are welcome brother. Wishing you all the best for your devops journey.
Understood the concept real quick ,excellent teaching
Thank you🙏
Thank you so much man, I'm starting with kubernetes and this is gold for me!!
Happy to hear this my friend.
your videos are to the point and information dense. Kudos, keep it up. #freelearning #opensource
Thank you🙏 ❤
secret is decoded not decrypted, great video, thanks
Thank you🙏
man you made all this very easy, thank you for the video
Thank you 🙏
Thanx a lot. Something that would be cool is to have a guide howto setup loki,mimir,tempo with grafana and prometheus in k8. Thanks!
Thanks for your feedback
"helm install grafana stable/grafana" is depricated.
you should use : helm install grafana grafana/grafana" instead.
otherwise great video. thank you for your help!
Thanks for the information. Unfortunately I cannot edit the existing video.
thanks sir, you're solve my problem
@@coopmech2546 You are welcome
now the repo stable/grafana got completely removed
helm install grafana stable/grafana
Error: INSTALLATION FAILED: repo stable not found
Dear Author, thank you for this amazing video. Also, I want to point out one error that you have made at 15:54 pod/prometheus-alertmanager READY 2/2 (Does not mean it have two pods or the count of pod is 2) (It means the running pod is having two containers and both are running.) or we can say that (number of running containers/Total number of containers)
Thanks
Thank you so much for the detailed information. Enjoyed watching the whole video. Thank you!!
You are welcome my friend.
Thank you for sharing excellent vedio
Happy to hear. You are welcome.
Very very informative ❤❤❤
Thank you
Awesome explained 😇
Thank you. Happy to hear this from you.
Amazing explained
Thank you
Thank you for the informative video! I have a quick question: What is the recommended approach for retrieving Prometheus data from a multi-node cluster? Should we deploy a DaemonSet or sidecar, or is there another preferred method?
It depends upon on how is your architecture and how you want to approach. Try thinking about pros and cons on different options.
amazing!! thank you so much.
You are welcome.
Grafana chart name has been updated btw. you need to run -> helm install grafana grafana/grafana
Thank you for sharing the info.
oooh bhai asli player tu nikla, thank you man !!
great videos! can you please tell which chart should I use?
- (kube-prometheus-stack): include prometheus operator which I believe is more powerful and easy to manage
- or (prometheus). currently running on our EKS cluster.
My concern is about future:
- We will be using this as centeral monitoring point for for both production and staging env. So I am thinking which chart will be good for ease of management and scalability?
Need to mention, we are deploying this with terraform helm provider.
thanks!
Kube prometheus stack will be easier one to deploy and use, you will have to go through the details of their roadmap plan as your future management of the system will be based on that.
@@Thetips4you thanks! got it
Thanks for this!
You are welcome
Thanks for the great video. I have one doubt, you have added Prometheus as source in Grafana UI, what happens if the grafana pod is recreated, do we need to add it again after pod recreation? or can we give a source to the Grafana directly in its helm chart ?
You can add the datasource config file in iac.
Amazing
Thank you
Thank you!
You are welcome.
I’ve created a server on which I’ve configured Prometheus and Grafana. On prometheus I’m monitoring my 10 VMs. I also want to monitor my AKS cluster and 2 Microk8s cluster on same Prometheus. How can I achieve my goal?
Can you please help me with how to do it on multiple AWS accounts without VPC peering? I need to get metrics from private IP subnets using any exporter and IAM role ... Please help
i was having issue doing the echo part but after using an online decoder i guess that worked too
Ok. thanks
when i entered this minikube service prometheus-server-ext it doesn't showing anything such URL or ip
and prometheus also not exposed on browser
Did you checked the running services?
@@Thetips4you services are running
Everything gone well but except exposed on browser with port
Will it help to monitor the the kubernetes cert expiration
You will have to configure the respective stanza for the monitor.
hi, if I want to have 2 replicas of Prometheus on 1 cluster, how do I edit the helm chart?
Pull chart from helm repository and make your modifications.
Hey, I want the mtrics of my pods which i have created (bascially deployments), so where is the prometheus configuration file, so that i can alter it according to me?
Yes. You can configure the Prometheus file.
I am unable to access the Prometheus and Grafana dashboards from my browser. However, when I run a curl command using :, I receive a response within the cluster. can you suggest me what can be the issue?
Are you running as node port or load balancer?
@@Thetips4you i am running as node port...can you suggest me how to run as load balancer
for the grafana installation as of 9th August, 2023 they're saying the chat is deprecated, pls what do we do?
What do you mean by chat? Did you installed latest version of Grafana?
helm install grafana grafana/grafana
How to add alerts in grafana values.yaml by using helm?
Do you mean package your grafana using helm?
as it seems to keep the history it should have to use Persistent volume. since we haven't configured it does it mean it will wipe out the history on the next restart? if not then how it is possible where it is keeping the data.
Can you be more clear on history of what?
I checked they are using PV and PVC using hostpath, which means the data would be stored on the host. Once the pods are recreated they will have the data back from there. I hope this answers your query.
Hi, After exposing the grafana clusterIP service as a Nodeport, I get ERR_CONNECTION_TIMED_OUT
when I type x.x.x.x:32578 in my browser. I run a 3 node k8s cluster with 1 controlplane and 2 worker nodes. Can you please help?
Did you opened the port in firewall ?
@@Thetips4you No, but it works now. I was using the controllplane IP thats was why it failed. thanks
How to configure Prometheus and grafana using ingress for secure login.
Thank you
You are welcome.
Great video, I have an interview Right Now and was great content, when can I donate or sponsor?
Thank you for your support. Currently I am not collecting any donations or sponsor.
nice !! make tutorials on teamcity too please !!
Will check on it.
Thanks,Where we can download custom dashboard template ?Please share link if any
grafana.com/grafana/dashboards/
I am not able to access. The link from minikube service --all of grafana and prometheus is not open in browser. What's the issue????????????
Are you getting some error?
I have installed minikube with docker driver on Ubuntu 20.04 and instlled helm and install Prometheus based on your video but iam not able to accessible from browser getting site can't be reached
Did you check the ports are not blocked in the firewall?
@@Thetips4you I have given all traffic in security groups may be iam thinking any compatibility issues
Are you using a cloud system?
@@Thetips4you yes AWS cloud
Finally I have successfully setup Prometheus and grafana using Ubuntu 20.04 in AWS cloud
I have configured the same but unable the see the data for CPU, Memory and IO same like your dashboard I see the N/A. Could you please share the steps to fix this
Are you facing any error?
@@Thetips4you no errors only metric data is not showing. I can see the metrics only for pods, deployments, containers.
After installing prometheus helm chart, when i go to check the pods or resources status it show resources in unhealthy state
Check the logs of the pod to see why it's failing.
My dear friend.. where is configured node_expoter in Prometheus.yml file. With port 9100 and .how can you recived metrics without configured of node_exporter in prometheus.yl file...... please reply
If you see the running pods, node exporter is also running as pod.
@@Thetips4you But in my case node exporter pod is pending state showing error msg " 1 node(s) didn't have free ports for the requested pod ports.
"
Amazing content
You are welcome. Thanks for your feedback.
helm install grafana stable/grafana
Error: INSTALLATION FAILED: repo stable not found
Why is this not installing ? any idea ?
Check the helm repo Or connectivity
try helm install grafana grafana/grafana
I installed Prometheus and grafana as per this video using helm on Azure Ubuntu VM
And exposed the svc using nodeport but not able to access the server
Please help
Not able to access means?
If the cluster itself goes down then how can we monitor?
You cannot.
@@Thetips4you so how we can avoid such issues?
Keep a high availability setup
i have pod error default prometheus-server-7d57c9697f-hqngs 1/2 Error 3 (30s ago) 74s
Grafana install at th-cam.com/video/dk2-_DbWb80/w-d-xo.html
Ok
unable to install grafana from stable
What is the error?
try helm install grafana grafana/grafana
Hello can you explain why I'm getting this error when installing prometheus?
helm install prometheus-release prometheus-community/prometheus
Error: template: prometheus/templates/NOTES.txt:86:46: executing "prometheus/templates/NOTES.txt" at : error calling index: index of untyped nil
Did you tried the installation again.
i check logs pod [root@k8smaster2 ~]# kubectl logs prometheus-server-7d57c9697f-hqngs
Defaulted container "prometheus-server-configmap-reload" out of: prometheus-server-configmap-reload, prometheus-server
2022/06/29 14:18:46 Watching directory: "/etc/config"
please help to check.
Hi, I was installing Prometheus. After "helm install prometheus prometheus-community/prometheus", I noticed that alertmanager and prometheus-server pods are in Pending state for more than 30 minutes. Appreciate any help. I have tried it twice - appreciate some help. Thx.
use the command kubectl describe and check the status of the pods. it should show you the reason why it is in pending state.
@@Thetips4you Hi there. I sent you an email. Can we connect for 5 mins to discuss an immediate engagement?
This is what I get from describing the pod towards the end.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 18m default-scheduler 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims.
Warning FailedScheduling 18m default-scheduler 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims.
Warning FailedScheduling 13m default-scheduler 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims.
arjun@k8s-controller-01-hp:~$
Looks like there are two pvc's but no pv's.
arjun@k8s-controller-01-hp:~$ kubectl get pv
No resources found
arjun@k8s-controller-01-hp:~$ kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
my-prometheus-alertmanager Pending 45m
my-prometheus-server Pending 45m
arjun@k8s-controller-01-hp:~$
There is some issue creating the persistent volume. I would suggest you to clean the release and delete the PV, PVC if anything there manually. Restart the docker service and then try again.