Skip to content

NGINX+ dashboard #1381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pleshakov opened this issue Dec 13, 2023 · 0 comments · Fixed by #1488
Closed

NGINX+ dashboard #1381

pleshakov opened this issue Dec 13, 2023 · 0 comments · Fixed by #1488
Assignees
Labels
enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented. size/small Estimated to be completed within ~2 days
Milestone

Comments

@pleshakov
Copy link
Contributor

pleshakov commented Dec 13, 2023

Support per-pod access to NGINX+ dashboard (like this one https://demo.nginx.com/ )

The dashboard is useful during troubleshooting, as it shows what happens in NGINX Plus at the moment. For example, status of upstream servers.

Similar feature in NIC -- https://docs.nginx.com/nginx-ingress-controller/logging-and-monitoring/status-page/#accessing-live-activity-monitoring-dashboard

Acceptance

  • The NGINX+ dashboard is enabled by default and only accessible via port forwarding.
  • Content is added to the NGINX+ doc to explain this feature.
@pleshakov pleshakov added the enhancement New feature or request label Dec 13, 2023
@ja20222 ja20222 added this to the v1.2.0 milestone Dec 14, 2023
@mpstefan mpstefan added refined Requirements are refined and the issue is ready to be implemented. size/small Estimated to be completed within ~2 days labels Jan 8, 2024
@sjberman sjberman self-assigned this Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented. size/small Estimated to be completed within ~2 days
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants