Open kirankumar-Athirala opened 2 weeks ago
Hi @kirankumar-Athirala
I don't know what might be going on, but the first idea that comes to my mind is that the prometheus operator is just looking in the namespace monitoring. There are some flags to configure this, but you have to look in the kube-prometheus-stack helm chart repo.
If I have time, I would try to deploy the same scenario as you and see what's happening.
BR, Álvaro
Hi Good Morning
I deployed kube prometheus stack for collecting the metrics from AMF, SMF, PCF and UPF.
I used kube-prometheus-stack "helm install kube-prom-stack prometheus-community/kube-prometheus-stack --namespace monitoring --create-namespac"
After the prometheus operator is deployed and running , I deployed open5gcore using helm chart as follows
helm install open5gs oci://registry-1.docker.io/gradiant/open5gs --version 2.2.0 --values values.yaml --namespace open5gs --create-namespace
I updated the values file to enable mtrics and service monitor.![image](https://github.com/Gradiant/5g-charts/assets/46919805/ff05e2fe-6f08-4b0c-9fbf-9fb7546e2139)
the core is deployed and i can see all the services are up and running and i can see metrics also enabled from amf pod logs![image](https://github.com/Gradiant/5g-charts/assets/46919805/523a8b87-3a5a-4822-a69f-9b5e15f67ee2)
But i am not able to see amf pod as a target in promethus![image](https://github.com/Gradiant/5g-charts/assets/46919805/f92806b7-e201-4c0e-98be-d0dc85379145)
I am not sure what configurations , i am missing to make this work . could you please help me to configure metrics to be scrapped by prometehus.
Thanks and Regards kirankumar Athirala