-
Notifications
You must be signed in to change notification settings - Fork 41
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
Metrics not supported? #136
Comments
Hello Marcin, Currently in our charts we support metrics for the AMF, SMF, UPF and PCF. If you take the AMF chart as an example, you can see in the values.yaml the argument Then, in the AMF config yaml ( Thus, you must set to Hope this helps you to make it work! |
Such a trivial issue - i thought that the metrics would be enabled by default, didn't notice that the default was set to "false"! Thanks for pointing me in the right direction |
Hi, Just for clarification, as @mmarquez999 said, the I have to agree with you, that is a pretty smart engineering, but it's not down to us, but the open-source projects we leverage on, such as prometheus-operator. Regards! |
Hi, I'm trying to access the NF metrics (https://open5gs.org/open5gs/docs/tutorial/04-metrics-prometheus/), and I see that the helm chart takes an argument for (containerPorts.metrics int, default is 9090). However the NF containers, in their yaml config files do not contain any mention of metrics, and running prometheus I can't scrap anything from the default ports (9090).
Are metrics supported at all in this chart?
I'm using the latest version from openverso https://gradiant.github.io/openverso-charts/
The text was updated successfully, but these errors were encountered: