-
Notifications
You must be signed in to change notification settings - Fork 2k
Closed
Labels
backlog candidatePull requests/issues that are candidates to be backlog itemsPull requests/issues that are candidates to be backlog itemsgood first issueIssues identified as good for first-time contributorsIssues identified as good for first-time contributorshelp wantedIssues identified as good community contribution opportunitiesIssues identified as good community contribution opportunities
Description
Describe the bug
In the NGINX Plus Grafana dashboard that is contained in this repo, if you have multiple upstreams configured in NIC, changing the selected upstream appears to have no effect.
To Reproduce
Steps to reproduce the behavior:
- Deploy NIC with Prometheus support
- Deploy a VirtualServer resource with multiple upstreams
- Install the dashboard and configure it per instructions in this repo
- Click the Upstream Server dropdown in the dashboard and click a specific upstream:
Expected behavior
The upstream-related graphs displayed in the dashboard should be filtered based on the selected dashboard.
Your environment
- Version of the Ingress Controller - 2.3.0
- Version of Kubernetes - 1.24
- Kubernetes platform: k3s
- Using NGINX Plus
Additional context
Metadata
Metadata
Assignees
Labels
backlog candidatePull requests/issues that are candidates to be backlog itemsPull requests/issues that are candidates to be backlog itemsgood first issueIssues identified as good for first-time contributorsIssues identified as good for first-time contributorshelp wantedIssues identified as good community contribution opportunitiesIssues identified as good community contribution opportunities