Skip to content
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

Document the ability store the custom dashboards generated for upstreams into folders other than general #5853

Open
pszeto opened this issue Jan 31, 2022 · 1 comment
Labels
stale Issues that are stale. These will not be prioritized without further engagement on the issue. Type: Docs

Comments

@pszeto
Copy link

pszeto commented Jan 31, 2022

Version

1.9.x (latest)

Describe the requested changes

This PR #3920 exposed the ability to store the custom grafana dashboards generated for discovered upstreams into folders other than general. This is useful because users can annotate their upstreams and segment the dashboards into different folders instead of all of them going to General.

Example of the patch command to change the upstream:
k patch upstream -n gloo-system default-petstore-v1-8080 --type merge -p '{"metadata":{"annotations":{"observability.solo.io/dashboard_folder_id": "68"}}}'

Link to any relevant existing docs

https://docs.solo.io/gloo-edge/latest/guides/observability/grafana/dashboards/#dynamically-generated-dashboards

Browser Information

No response

Additional Context

Screen Shot 2022-01-31 at 4 45 21 PM

Copy link

github-actions bot commented Jun 2, 2024

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.

@github-actions github-actions bot added the stale Issues that are stale. These will not be prioritized without further engagement on the issue. label Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues that are stale. These will not be prioritized without further engagement on the issue. Type: Docs
Projects
None yet
Development

No branches or pull requests

1 participant