nginx_ingress_controller_requests is missing for Ingress that has had no requests

[lambchr]

NGINX Ingress controller version: 0.30.0

Kubernetes version (use kubectl version): 1.15

Environment:

• EKS k8s cluster

What happened:

The nginx_ingress_controller_requests metric was missing for Ingresses that have had 0 requests. I queried nginx_ingress_controller_requests == 0 for our prometheus metrics and found no time series.

What you expected to happen:

I expected ingresses that have had no requests sent to them to have a nginx_ingress_controller_requests metric with a count of 0 rather than not being present.

How to reproduce it:

• I deployed a test Ingress object (very basic config) with the host name set
• I waited for the Ingress controller to show the host and address, I've seen other bugs raised that state this metric won't show if the host isn't set but I don't think that applies here

$ kubectl --context <CONTEXT> -n <NAMESPACE> get ing test
NAME       HOSTS          ADDRESS                 PORTS     AGE
test       <DOMAIN>  <LB_ADDRESS>      <PORTS>   7h40m

• I looked for the metric in prometheus for this ingress but couldn't find it nginx_ingress_controller_requests{ingress="test"}
• I also exec'd to a pod on the cluster and hit the NGINX controller's /metrics endpoint to check if our prometheus stack was filtering out the metric, but it didn't appear there either

Anything else we need to know:

Please let me know if you need any other info from me, thanks for your time :)

/kind bug

[kundan2707]

/ assign

[strongjz]

Please upgrade to 0.46.0 and see if this is still an issue.

[strongjz]

/triage needs-information

[lambchr]

Hi @strongjz sorry for the delayed response. I upgrade to 0.47.0 and repeated my above test (created new debug ingress, waited for host and address to appear, checked if metric appeared) and could still not see any nginx_ingress_controller_requests metrics from the /metrics endpoint of any NGINX pod in the cluster. When I curled my new debug ingress and checked the NGINX pods /metrics endpoint again it showed me an nginx_ingress_controller_requests metric for that ingress. Please let me know if you need any more info from me :)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[lambchr]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[lambchr]

/remove-lifecycle stale

Hey @strongjz do you need any more information?

[philwelz]

i can confirm this behavior on version v1.0.4 / 4.0.6 where the metric nginx_ingress_controller_requests is missing until you do any request (for example curl) to an ingress resource.