Cherry-pick #21052 to 7.x: Add ingress controller dashboards#21054
Merged
ChrsMark merged 1 commit intoelastic:7.xfrom Sep 14, 2020
Merged
Cherry-pick #21052 to 7.x: Add ingress controller dashboards#21054ChrsMark merged 1 commit intoelastic:7.xfrom
ChrsMark merged 1 commit intoelastic:7.xfrom
Conversation
Signed-off-by: chrismark <chrismarkou92@gmail.com> (cherry picked from commit 54ea284)
Contributor
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
Contributor
kaiyan-sheng
approved these changes
Sep 14, 2020
This file contains hidden or 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
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.
Cherry-pick of PR #21052 to 7.x branch. Original message:
What does this PR do?
This PR adds 2 Dashboards based ingress nginx controller fileset (implemented with #16197).
Most of the fields of
ingress_controllerare the same withaccessfileset ofnginxmodule. In this most of the visualisations of these new dashboards are just copied from pre existing ones and modified accordingly while others are re-used. There are also some completely new ones. More spcifically:fileset.nameWhy is it important?
To provide out of the box Dashboards for ingress controller service monitoring.
How to test this PR locally
kubectl -n kube-system logs -f nginx-ingress-controller-6fc5bcc8c9-zm8zv >> /tmp/ingresspodRelated issues
Screenshots