I Forgot to mention that I have installed Prometheus with the helm chart
and the following command:
helm install prometheus \
--namespace=monitoring \
--set server.ingress.hosts={my.address.com} \
--set server.ingress.tls[0].hosts[0]=my.address.com \
--set server.ingress.tls[0].secretName=my-address-com-tls \
--set server.ingress.enabled=true \
--set server.ingress.annotations.'kubernetes\.io/ingress\.class'=nginx \
--set server.ingress.annotations.'cert-manager\.io/issuer'=monitoring-issuer \
stable/prometheus
And didn't change anything else...
On Wednesday, May 13, 2020 at 5:55:10 PM UTC+2, Nathaniel Cohen wrote:
>
> I have set up Prometheus in my Kubernetes Google Cluster and it collects
> many services but not the NodeJS micro-service I have created.
>
> The NodeJS service is detected by Prometheus because I can see it in the
> status -> Service Discovery but it is not an active target.
>
> [image: Screenshot 2020-05-13 at 17.00.38.png]
>
>
> I also used an nginx-ingress to expose my NodeJS service to the internet
> and I can even navigate to the /metrics endpoint:
>
>
> [image: Screenshot 2020-05-13 at 17.09.26.png]
>
>
>
> My NodeJS service uses express and appmetrics
> <https://www.npmjs.com/package/appmetrics-prometheus/v/3.1.0> is set up
> for the `/metrics` endpoint.
>
> How can I debug this? What can I do to check why Prometheus is failing to
> make this service an active target?
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/85687f76-214c-40a7-9c90-564ee387e182%40googlegroups.com.
