Add per-domain ACME metrics for requests

[christianhuening]

Is your feature request related to a problem? Please describe.
we sometimes run into the issue that developers exceed our weekly limits for certificate requests for certain domains (due to deletion and standup of dev environments).

Describe the solution you'd like
Though this can be mitigated by helm chart improvements etc. it would be super helpful to have a per-domain request metric exposed from the Cert-Manager

Describe alternatives you've considered
Simply make sure Ingress resources etc are not rolled out everytime in dev cluster. But we need visibility

Environment details (if applicable):

• Kubernetes version (e.g. v1.10.2): v1.15.10
• Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): bare-metal, on-prem
• cert-manager version (e.g. v0.4.0): v0.13.0
• Install method (e.g. helm or static manifests): helm

/kind feature

[munnerz]

Hm, the issue here is that it will greatly increase the cardinality of our metrics if there are lots of domains in a cluster. I'm not 100% sure how to mitigate this given that's exactly what you want, but I don't think we can expose this metric by default at least.

/priority awaiting-more-evidence
/area monitoring

[christianhuening]

hm well... having the option would great i think. Other than hiding it behind a flag i dont have a good idea I am afraid 🤔

[christianhuening]

what if we'd only take the total number of requests and not per-domain?

[jetstack-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

[jetstack-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

[jetstack-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

[jetstack-bot]

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.