This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
Monitoring extension documentation addition #2740
Merged
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
CecileRobertMichon
suggested changes
Apr 20, 2018
docs/kubernetes/monitoring.md
Outdated
| @@ -65,6 +66,16 @@ Once you have opened the UI, you can explore node stats (CPU, Memory, etc...) un | |||
|
|
|||
|  | |||
|
|
|||
| ## Monitoring extension | |||
|
|
|||
| A quick way to scaffold out cloud-native and open source monitoring components is to use the [acs-engine monitoring extension](https://github.com/Azure/acs-engine/tree/master/extensions/prometheus-grafana-k8s). For details on how to use the monitoring extension, please refer to the extension documentation. By embedding the extension in your apimodel, the extension will do much of the work to create a monitoring solution in your cluster, which includes the following... | |||
There was a problem hiding this comment.
Is it possible to make extension documentation a link?
There was a problem hiding this comment.
which includes the following... -->which includes the following:
There was a problem hiding this comment.
Absolutely, changes made!
docs/kubernetes/monitoring.md
Outdated
| - [Prometheus](https://prometheus.io/) for metrics collection and storage | ||
| - [Grafana](https://grafana.com/) for dashboard and visualizations | ||
|
|
||
| The extension wires up these components together. Post-deplyoment of the Kubernetes cluster, you just have to retrieve Grafana username password secret and target your browser to the Grafana endpoint. There is already a pre-loaded Kubernetes cluster monitoring dashboard, so out-of-the-box you will have meaningful monitoring points with the extensibility that Prometheus and Grafana offer you. |
There was a problem hiding this comment.
you just have to retrieve Grafana username password secret and target your browser are there some missing commas here between username, password and secret?
There was a problem hiding this comment.
I'll reword this so it is more clear. Thanks!
CecileRobertMichon
approved these changes
Apr 20, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What this PR does / why we need it: adds an excerpt explaining the option of using the acs-engine monitoring extension for monitoring a Kubernetes cluster deployed from acs-engine
If applicable:
// cc @ritazh