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

Performance / custom dashboards: new configs #243

Merged
merged 2 commits into from
Feb 3, 2021
Merged

Performance / custom dashboards: new configs #243

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aa318e3
Performance / custom dashboards: new configs
jotak Feb 3, 2021
9081700
mazz feedback
jotak Feb 3, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
15 changes: 13 additions & 2 deletions deploy/kiali/kiali_cr.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -408,15 +408,26 @@ spec:
# In this case, you would set "external_services.grafana.auth.password" to "secret:myGrafanaCredentials:myGrafanaPw".
#
# **Custom-dashboards settings:
# enabled: enable or disable custom dashboards, including the dashboards discovery process. Default: true.
# discovery_auto_threshold: Threshold of the number of pods, for a given Application or Workload, above which dashboards discovery will be skipped
# This setting only takes effect when discovery_enabled is set to 'auto'.
# discovery_enabled: Enable, disable or set 'auto' mode to the dashboards discovery process. If set to true, Kiali
# will always try to discover dashboards based on metrics. Note that it can generate performance penalties while
# discovering dashboards for workloads having many pods (thus many metrics).
# When set to 'auto', Kiali will skip dashboards discovery for workloads with more than a configured threshold of pods
# (see 'discovery_auto_threshold'). When discovery is disabled or auto/skipped, it is still possible to tie workloads
# with dashboards through annotations on pods (refer to the doc https://kiali.io/documentation/latest/runtimes-monitoring/#pods-annotations)
# Allowed values: true, false, auto.
# enabled: Enable or disable custom dashboards, including the dashboards discovery process. Default: true.
# is_core_component: Used in the Components health feature. When true, the unhealthy scenarios will be raised as errors. Otherwise, they will be raised as a warning.
# namespace_label: Prometheus label name used for identifying namespaces in metrics for custom dashboards.
# Default is "kubernetes_namespace". It is quite common to use just "namespace" as well, depending on your Prometheus configuration.
# prometheus: please check the section below about Prometheus-specific settings: they are identical. The Prometheus
# prometheus: Please check the section below about Prometheus-specific settings: they are identical. The Prometheus
# configuration defined here is dedicated to fetching custom dashboards, hence allowing to use a different instance
# of Prometheus. If omitted, the same Prometheus as for Istio metrics will be reused for custom dashboards.
# ---
# custom_dashboards:
# discovery_auto_threshold: 10
# discovery_enabled: auto
# enabled: true
# is_core_component: false
# namespace_label: "kubernetes_namespace"
Expand Down
2 changes: 2 additions & 0 deletions roles/default/kiali-deploy/defaults/main.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,8 @@ kiali_defaults:

external_services:
custom_dashboards:
discovery_auto_threshold: 10
discovery_enabled: "auto"
enabled: true
is_core_component: false
namespace_label: ""
Expand Down