Provide some default Prometheus alerts

[jmreicha]

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): prometheus alerts, metric alerts

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature request

With the addition of the Grafana dashboard it would also be useful to have a set of "default" rules that can be applied to Prometheus to monitor the Nginx ingress.

In my searching I have been able to find some other projects that provide some level of alerting for various metrics. Kubernetes and kube-prometheus for example provide jsonnet for creating the rules.

There is also the Monitoring Mixin Design Doc which outlines a way to package rules, alerts and dashboards, which may be a way to provide these things.

NGINX Ingress controller version: v0.21.0

Kubernetes version (use kubectl version): 1.10.x

Environment: NA

[BrianChristie]

I think it would be great to have a monitoring-mixin for ingress-nginx. It may be a bit tricky to figure out what alerts are appropriate, because I think we might want the following separate:

• Control plane alerts for ingress-nginx
• Data plane alerts for cluster-applications which use Nginx ingress and are experiencing failures

For example, as a cluster-operator, I don't necessarily want to be paged when a cluster-users application is failing. But equally I'd like to provide an easy way for cluster-users to get alerts/pages when their application is failing.

Does anyone have thoughts on how these can be cleanly separated?

[fejta-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 sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jmreicha]

/remove-lifecycle stale

[HaveFun83]

Will be really nice to have a baseline for this topic.

[fejta-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 sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jmreicha]

/remove-lifecycle stale

[fejta-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 sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jmreicha]

/remove-lifecycle stale

[fejta-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 sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-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 sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[jmreicha]

/remove-lifecycle rotten

[nlamirault]

Any news ?

[fejta-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 sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[sandhose]

/remove-lifecycle stale

[cmluciano]

I'm not sure if this is something that should be provided by default since alerts are very specific to a given organization. If the request is for mixin or doc outlining some general advice, then I'm happy to review a PR.

/triage needs-information

[fejta-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 sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-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 sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[nlamirault]

/remove-lifecycle stale

[fejta-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 sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-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 sig-contributor-experience at kubernetes/community.
/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.