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.

Sign up for GitHub

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

Jump to bottom

docs: add more details in the example monitoring stack setup #21444

Closed
Tracked by #21438
, #21503
...
dkwon17 opened this issue Jun 7, 2022 · 3 comments
Closed
Tracked by #21438
, #21503
...

docs: add more details in the example monitoring stack setup #21444

dkwon17 opened this issue Jun 7, 2022 · 3 comments
Assignees
@dkwon17
Labels
area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@dkwon17
Copy link
Contributor

dkwon17 commented Jun 7, 2022

Is your enhancement related to a problem? Please describe

In the Prometheus/Grafana docs: https://www.eclipse.org/che/docs/next/administration-guide/monitoring-the-dev-workspace-operator/, we walk the reader through an example Prometheus Grafana setup for monitoring the DWO and Che-Server Java metrics.

There are a few "fill in the blank" sections in the provided yaml files:
image

It can be difficult to determine what the correct values are.

Describe the solution you'd like

Add a few sentences explaining how to fill in these blanks.

It would be nice to mention:

  • What namespace Prometheus/Grafana is installed in, for the example setup
  • What service account is the Prometheus pod using
  • Mention that a route/ingress can be created to access the Prometheus and Grafana dashboards

Describe alternatives you've considered

No response

Additional context

No response
@dkwon17 dkwon17 added kind/enhancement A feature request - must adhere to the feature request template. area/doc Issues related to documentation team/doc labels Jun 7, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jun 7, 2022
@dkwon17
Copy link
Contributor Author

dkwon17 commented Jun 7, 2022

I am interested in taking a look at this

@ibuziuk ibuziuk mentioned this issue Jun 8, 2022
Closed
64 tasks
@amisevsk amisevsk added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jun 10, 2022
@dkwon17 dkwon17 mentioned this issue Jun 17, 2022
Merged
6 tasks
@themr0c
Copy link
Contributor

themr0c commented Jun 28, 2022

Cloned in https://issues.redhat.com/browse/RHDEVDOCS-4196

@ibuziuk ibuziuk mentioned this issue Jun 28, 2022
Closed
68 tasks
@dkwon17 dkwon17 closed this as completed Jun 28, 2022
@dkwon17
Copy link
Contributor Author

dkwon17 commented Jun 28, 2022

Closed thanks to eclipse-che/che-docs#2379 being merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dkwon17 dkwon17

Labels
area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@themr0c @amisevsk @che-bot @dkwon17