-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
-
Using Docker Hub image jenkins/jenkins:lts deployed with Helm chart stable/jenkins
Jenkins ver. 2.190.2
Prometheus metrics plugin 2.0.6
Whether you're running Jenkins directly or in a container like Tomcat (which one, in which version?) Deployed using Docker Hub image jenkins/jenkins:lts
Whether Jenkins is accessed through a reverse proxy (if so, how is it configured?) Using Kubernetes service and ingress, manifests can be provided.
Chrome Version 78.0.3904.70 (Official Build) (64-bit)Using Docker Hub image jenkins/jenkins:lts deployed with Helm chart stable/jenkins Jenkins ver. 2.190.2 Prometheus metrics plugin 2.0.6 Whether you're running Jenkins directly or in a container like Tomcat (which one, in which version?) Deployed using Docker Hub image jenkins/jenkins:lts Whether Jenkins is accessed through a reverse proxy (if so, how is it configured?) Using Kubernetes service and ingress, manifests can be provided. Chrome Version 78.0.3904.70 (Official Build) (64-bit)
Using a custom path for Prometheus metrics collection recieves a 404.
Please see attache screenshots.
STR change Prometheus Path on Jenkins configuration page. Navigate to path and observe 404.
