docs: cluster observability documentation and dashboard improvements #9391
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for determined-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
kkunapuli
changed the title
tara-det-ai
reviewed
May 20, 2024
docs/release-notes/observability.st
Outdated
|
|
||
| Kubernetes: Add Determined resource information such as `workspace` and `task ID` as pod labels. This improvement facilitates better resource tracking and management within Kubernetes environments. | ||
|
|
||
| Configuration: Introduce a DCGM Helm chart and Prometheus configuration to the `tools/observability` directory. Additionally, two new dashboards, "API Monitoring" and "Resource Utilization", have been added to improve observability and operational insight. |
There was a problem hiding this comment.
this is an "st" file, please change it to an *.rst file
"docs/release-notes/observability.st" should be "docs/release-notes/observability.rst"
There was a problem hiding this comment.
Good catch - thank you!
NicholasBlaskey
approved these changes
May 20, 2024
| Discover how to enable a Grafana dashboard to monitor Determined hardware and system metrics. | ||
| Determined provides a Prometheus endpoint that contains mappings between internal task, GPU, and | ||
| container definitions, which are used by Prometheus to collect relevant metrics on a cluster running | ||
| Determined. The endpoint is not enabled by default but can be enabled in the master configuration |
There was a problem hiding this comment.
prometheus should be enabled by default now
There was a problem hiding this comment.
Nice catch! Thank you!
I inverted the sentence The endpoint is enabled by default but can be disabled in the master configuration file.
tara-det-ai
approved these changes
May 20, 2024
Co-authored-by: Tara Charter <tara.charter@hpe.com>
kkunapuli
force-pushed
the
observability_feature_branch
branch
from
f16f30d
to
9ec1196
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket
RM-293
Description
Merging Cluster Observability feature branch to main. New instructions for setting up observability in Kubernetes environments, along with updated dashboards.
Test Plan
None needed.
Checklist
docs/release-notes/.See Release Note for details.