From 442c2a5676524c18ef03cfa8c7d680d14e3d3284 Mon Sep 17 00:00:00 2001 From: Shayna Finocchiaro <66699024+shaynafinocchiaro@users.noreply.github.com> Date: Mon, 14 Feb 2022 17:38:10 -0500 Subject: [PATCH 1/5] refactor helm install steps --- content/docs/observability/deployment/helm.md | 85 +++++++------------ 1 file changed, 30 insertions(+), 55 deletions(-) diff --git a/content/docs/observability/deployment/helm.md b/content/docs/observability/deployment/helm.md index 07708c86f7..f56d8aca63 100644 --- a/content/docs/observability/deployment/helm.md +++ b/content/docs/observability/deployment/helm.md @@ -10,60 +10,54 @@ The Container Storage Modules (CSM) for Observability Helm chart bootstraps an O ## Prerequisites -- A [supported](../../../csidriver/#features-and-capabilities) CSI Driver is deployed -- The cert-manager CustomResourceDefinition resources are created. +- A [supported](../../#supported-csi-drivers) Dell CSI Driver is deployed - ```console - $ kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.5.3/cert-manager.crds.yaml - ``` - -## Copy the CSI Driver Entities +## Install the CSM for Observability Helm Chart +**Steps** +1. Create a namespace where you want to install the module `kubectl create namespace karavi` -Copy the config Secret from the Dell CSI Driver namespace into the namespace where CSM for Observability is deployed. +2. Install cert-manager CRDs `kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.6.1/cert-manager.crds.yaml` -### PowerFlex +3. Add the Dell Helm Charts repo `helm repo add dell https://dell.github.io/helm-charts` -```console -$ kubectl get secret vxflexos-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f - -``` +4. Copy only the deployed CSI driver entities to the Observability namespace + #### PowerFlex -If CSM-Authorization is enabled, perform the following steps. + 1. Copy the config Secret from the CSI PowerFlex namespace into the CSM for Observability namespace: -Copy the driver configuration parameters ConfigMap into the namespace where CSM for Observability is deployed. + `kubectl get secret vxflexos-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -` -``` -$ kubectl get configmap vxflexos-config-params -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f - -``` + If [CSM for Authorization is enabled](../../../authorization/deployment/#configuring-a-dell-emc-csi-driver-with-csm-for-authorization) for CSI PowerFlex, perform the following steps: -Create the `karavi-authorization-config` Secret by following step 2 in [Configuring a Dell EMC CSI Driver](../../../authorization/deployment/#configuring-a-dell-emc-csi-driver) but use the [CSM_NAMESPACE]. + 2. Copy the driver configuration parameters ConfigMap from the CSI PowerFlex namespace into the CSM for Observability namespace: + + `kubectl get configmap vxflexos-config-params -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -` -Create the `proxy-server-root-certificate` Secret by following step 3 in [Configuring a Dell EMC CSI Driver](../../../authorization/deployment#configuring-a-dell-emc-csi-driver) but use the [CSM_NAMESPACE]. + 3. Copy the `karavi-authorization-config`, `proxy-server-root-certificate`, `proxy-authz-tokens` Secret from the CSI PowerFlex namespace into the CSM for Observability namespace: -Generate a token and apply it to the [CSM_NAMESPACE] by following [Generate a Token](../../../authorization/deployment/#generate-a-token). + `kubectl get secret karavi-authorization-config proxy-server-root-certificate proxy-authz-tokens -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -` -__Note__: The target namespace must exist before executing this command. + #### PowerStore -### PowerStore + 1. Copy the config Secret from the CSI PowerStore namespace into the CSM for Observability namespace: -```console -$ kubectl get secret powerstore-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f - -``` + `kubectl get secret powerstore-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f -` -__Note__: The target namespace must exist before executing this command. +5. Configure the [parameters](#configuration) and install the CSM for Observability Helm Chart -## Add the Repo + A default values.yaml file is located [here](https://github.com/dell/helm-charts/blob/main/charts/karavi-observability/values.yaml) that can be used for installation. This can be copied into a file named `myvalues.yaml` and either used as is or modified accordingly. -```console -$ helm repo add dell https://dell.github.io/helm-charts -``` + `helm install karavi-observability dell/karavi-observability -n [CSM_NAMESPACE] -f myvalues.yaml` -## Installing the Chart + Alternatively, you can specify each parameter using the '--set key=value[,key=value]' and/or '--set-file key=value[,key=value] arguments to 'helm install'. For example: -```console -$ helm install karavi-observability dell/karavi-observability -n [CSM_NAMESPACE] --create-namespace -``` - -The [configuration](#configuration) section below lists all the parameters that can be configured during installation + ```console + $ helm install karavi-observability dell/karavi-observability -n [CSM_NAMESPACE] \ + --set-file karaviTopology.certificateFile= \ + --set-file karaviTopology.privateKeyFile= \ + --set-file otelCollector.certificateFile= \ + --set-file otelCollector.privateKeyFile= + ``` ## Configuration @@ -114,22 +108,3 @@ The following table lists the configurable parameters of the CSM for Observabili | `karaviMetricsPowerstore.zipkin.uri` | URI of a Zipkin instance where tracing data can be forwarded | | | `karaviMetricsPowerstore.zipkin.serviceName` | Service name used for Zipkin tracing data | `metrics-powerstore`| | `karaviMetricsPowerstore.zipkin.probability` | Percentage of trace information to send to Zipkin (Valid range: 0.0 to 1.0) | `0` | - - -Specify each parameter using the '--set key=value[,key=value]' and/or '--set-file key=value[,key=value] arguments to 'helm install'. For example: - -```console -$ helm install karavi-observability dell/karavi-observability -n [CSM_NAMESPACE] --create-namespace \ - --set-file karaviTopology.certificateFile= \ - --set-file karaviTopology.privateKeyFile= \ - --set-file otelCollector.certificateFile= \ - --set-file otelCollector.privateKeyFile= -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example: - -```console -$ helm install karavi-observability dell/karavi-observability -n [CSM_NAMESPACE] --create-namespace -f values.yaml - ``` - -__Note__: You can use the default [values.yaml](https://github.com/dell/helm-charts/blob/main/charts/karavi-observability/values.yaml) \ No newline at end of file From 2c916a4d3e7599e86d3fafd4f8a3ec5785660f79 Mon Sep 17 00:00:00 2001 From: Shayna Finocchiaro <66699024+shaynafinocchiaro@users.noreply.github.com> Date: Mon, 14 Feb 2022 18:55:01 -0500 Subject: [PATCH 2/5] add notes about topology and authorization --- content/docs/observability/_index.md | 4 ++-- content/docs/observability/deployment/helm.md | 4 ++++ content/docs/observability/deployment/offline.md | 15 +++++++++++++-- content/docs/observability/deployment/online.md | 5 +++++ 4 files changed, 24 insertions(+), 4 deletions(-) diff --git a/content/docs/observability/_index.md b/content/docs/observability/_index.md index 3eb2af6d47..7c96d5c737 100644 --- a/content/docs/observability/_index.md +++ b/content/docs/observability/_index.md @@ -14,14 +14,14 @@ Description: > Metrics data is collected and pushed to the [OpenTelemetry Collector](https://github.com/open-telemetry/opentelemetry-collector), so it can be processed, and exported in a format consumable by Prometheus. SSL certificates for TLS between nodes are handled by [cert-manager](https://github.com/jetstack/cert-manager). -CSM for Observability is composed of several services, each living in its own GitHub repository. Contributions can be made to this repository or any of the CSM for Observability repositories listed below. +CSM for Observability is composed of several services, each living in its own GitHub repository, that can be installed following one of the three deployments we support [here](deployment). Contributions can be made to this repository or any of the CSM for Observability repositories listed below. {{}} | Name | Repository | Description | | ---- | --------- | ----------- | | Performance Metrics for PowerFlex | [CSM Metrics for PowerFlex](https://github.com/dell/karavi-metrics-powerflex) | Performance Metrics for PowerFlex captures telemetry data about Kubernetes storage usage and performance obtained through the CSI (Container Storage Interface) Driver for Dell EMC PowerFlex. The metrics service pushes it to the OpenTelemetry Collector, so it can be processed, and exported in a format consumable by Prometheus. Prometheus can then be configured to scrape the OpenTelemetry Collector exporter endpoint to provide metrics so they can be visualized in Grafana. Please visit the repository for more information. | | Performance Metrics for PowerStore | [CSM Metrics for PowerStore](https://github.com/dell/csm-metrics-powerstore) | Performance Metrics for PowerStore captures telemetry data about Kubernetes storage usage and performance obtained through the CSI (Container Storage Interface) Driver for Dell EMC PowerStore. The metrics service pushes it to the OpenTelemetry Collector, so it can be processed, and exported in a format consumable by Prometheus. Prometheus can then be configured to scrape the OpenTelemetry Collector exporter endpoint to provide metrics so they can be visualized in Grafana. Please visit the repository for more information. | -| Volume Topology | [CSM Topology](https://github.com/dell/karavi-topology) | Topology provides Kubernetes administrators with the topology data related to containerized storage that is provisioned by a CSI (Container Storage Interface) Driver for Dell EMC storage products. Please visit the repository for more information. | +| Volume Topology | [CSM Topology](https://github.com/dell/karavi-topology) | Topology provides Kubernetes administrators with the topology data related to containerized storage that is provisioned by a CSI (Container Storage Interface) Driver for Dell EMC storage products. The Topology service is enabled by default as part of the CSM for Observability Helm Chart [values file](https://github.com/dell/helm-charts/blob/main/charts/karavi-observability/values.yaml). Please visit the repository for more information. | {{
}} ## CSM for Observability Capabilities diff --git a/content/docs/observability/deployment/helm.md b/content/docs/observability/deployment/helm.md index f56d8aca63..bc360d1971 100644 --- a/content/docs/observability/deployment/helm.md +++ b/content/docs/observability/deployment/helm.md @@ -49,6 +49,10 @@ The Container Storage Modules (CSM) for Observability Helm chart bootstraps an O `helm install karavi-observability dell/karavi-observability -n [CSM_NAMESPACE] -f myvalues.yaml` + __Note:__ + - The default `values.yaml` is configured to deploy the CSM for Observability Topology service on install. + - If CSM for Authorization is enabled for CSI PowerFlex, the `karaviMetricsPowerflex.authorization` parameters must be properly configured in your values file for CSM Observability. + Alternatively, you can specify each parameter using the '--set key=value[,key=value]' and/or '--set-file key=value[,key=value] arguments to 'helm install'. For example: ```console diff --git a/content/docs/observability/deployment/offline.md b/content/docs/observability/deployment/offline.md index 22fd1f1e3f..b58697e524 100644 --- a/content/docs/observability/deployment/offline.md +++ b/content/docs/observability/deployment/offline.md @@ -125,7 +125,15 @@ To perform an offline installation of a Helm chart, the following steps should b [user@anothersystem /home/user/offline-karavi-observability-bundle/helm]# kubectl get secret vxflexos-config -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f - ``` - If CSM-Authorization is enabled, perform the additional steps at [Copy the CSI Driver Entities](../helm/#copy-the-csi-driver-entities) to create the required Secrets and ConfigMap and fill in the authorization parameters in the values.yaml. + If [CSM for Authorization is enabled](../../../authorization/deployment/#configuring-a-dell-emc-csi-driver-with-csm-for-authorization) for CSI PowerFlex, perform the following steps: + + ``` + [user@anothersystem /home/user/offline-karavi-observability-bundle/helm]# kubectl get configmap vxflexos-config-params -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f - + ``` + + ``` + [user@anothersystem /home/user/offline-karavi-observability-bundle/helm]# kubectl get secret karavi-authorization-config proxy-server-root-certificate proxy-authz-tokens -n [CSI_DRIVER_NAMESPACE] -o yaml | sed 's/namespace: [CSI_DRIVER_NAMESPACE]/namespace: [CSM_NAMESPACE]/' | kubectl create -f - + ``` CSI Driver for PowerStore ``` @@ -134,7 +142,10 @@ To perform an offline installation of a Helm chart, the following steps should b 4. Now that the required images have been made available and the Helm chart's configuration updated with references to the internal registry location, installation can proceed by following the instructions that are documented within the Helm chart's repository. - **Note:** Optionally, you could provide your own [configurations](../helm/#configuration). A sample values.yaml file is located [here](https://github.com/dell/helm-charts/blob/main/charts/karavi-observability/values.yaml). + **Note:** + - Optionally, you could provide your own [configurations](../helm/#configuration). A sample values.yaml file is located [here](https://github.com/dell/helm-charts/blob/main/charts/karavi-observability/values.yaml). + - The default `values.yaml` is configured to deploy the CSM for Observability Topology service on install. + - If CSM for Authorization is enabled for CSI PowerFlex, the `karaviMetricsPowerflex.authorization` parameters must be properly configured. ``` [user@anothersystem /home/user/offline-karavi-observability-bundle/helm]# helm install -n install-namespace app-name karavi-observability diff --git a/content/docs/observability/deployment/online.md b/content/docs/observability/deployment/online.md index 294b834627..87ab82b411 100644 --- a/content/docs/observability/deployment/online.md +++ b/content/docs/observability/deployment/online.md @@ -92,6 +92,11 @@ To perform an online installation of CSM for Observability, the following steps The following example will install CSM for Observability into the CSM namespace. A sample values.yaml file is located [here](https://github.com/dell/helm-charts/blob/main/charts/karavi-observability/values.yaml). This can be copied into a file named `myvalues.yaml` and modified accordingly for the installer command below. Configuration options are outlined in the [Helm chart deployment section](../helm#configuration). + + __Note:__ + - The default `values.yaml` is configured to deploy the CSM for Observability Topology service on install. + - If CSM for Authorization is enabled for CSI PowerFlex, the `karaviMetricsPowerflex.authorization` parameters must be properly configured in `myvalues.yaml` for CSM Observability. + ``` [user@system /home/user/karavi-observability/installer]# ./karavi-observability-install.sh install --namespace [CSM_NAMESPACE] --values myvalues.yaml --------------------------------------------------------------------------------- From 9a75c7bbaeb22c03e39ba7e1dc1ad4b707052d04 Mon Sep 17 00:00:00 2001 From: Shayna Finocchiaro <66699024+shaynafinocchiaro@users.noreply.github.com> Date: Tue, 15 Feb 2022 10:09:33 -0500 Subject: [PATCH 3/5] move prereqs --- content/docs/observability/deployment/_index.md | 5 ----- content/docs/observability/deployment/helm.md | 9 ++++++--- content/docs/observability/deployment/offline.md | 5 +++++ content/docs/observability/deployment/online.md | 5 +++++ 4 files changed, 16 insertions(+), 8 deletions(-) diff --git a/content/docs/observability/deployment/_index.md b/content/docs/observability/deployment/_index.md index b8b9750569..321c8d687a 100644 --- a/content/docs/observability/deployment/_index.md +++ b/content/docs/observability/deployment/_index.md @@ -12,11 +12,6 @@ CSM for Observability can be deployed in one of three ways: - [CSM for Observability Installer](./online) - [CSM for Observability Offline Installer](./offline) -## Prerequisites - -- Helm 3.3 -- The deployment of one or more [supported](../#supported-csi-drivers) Dell EMC CSI drivers - ## Post Installation Dependencies The following third-party components are required in the same Kubernetes cluster where CSM for Observability has been deployed: diff --git a/content/docs/observability/deployment/helm.md b/content/docs/observability/deployment/helm.md index bc360d1971..141ffe94ab 100644 --- a/content/docs/observability/deployment/helm.md +++ b/content/docs/observability/deployment/helm.md @@ -10,7 +10,8 @@ The Container Storage Modules (CSM) for Observability Helm chart bootstraps an O ## Prerequisites -- A [supported](../../#supported-csi-drivers) Dell CSI Driver is deployed +- Helm 3.3 +- The deployment of one or more [supported](../#supported-csi-drivers) Dell CSI drivers ## Install the CSM for Observability Helm Chart **Steps** @@ -47,12 +48,14 @@ The Container Storage Modules (CSM) for Observability Helm chart bootstraps an O A default values.yaml file is located [here](https://github.com/dell/helm-charts/blob/main/charts/karavi-observability/values.yaml) that can be used for installation. This can be copied into a file named `myvalues.yaml` and either used as is or modified accordingly. - `helm install karavi-observability dell/karavi-observability -n [CSM_NAMESPACE] -f myvalues.yaml` - __Note:__ - The default `values.yaml` is configured to deploy the CSM for Observability Topology service on install. - If CSM for Authorization is enabled for CSI PowerFlex, the `karaviMetricsPowerflex.authorization` parameters must be properly configured in your values file for CSM Observability. + ```console + $ helm install karavi-observability dell/karavi-observability -n [CSM_NAMESPACE] -f myvalues.yaml + ``` + Alternatively, you can specify each parameter using the '--set key=value[,key=value]' and/or '--set-file key=value[,key=value] arguments to 'helm install'. For example: ```console diff --git a/content/docs/observability/deployment/offline.md b/content/docs/observability/deployment/offline.md index b58697e524..01818b08bc 100644 --- a/content/docs/observability/deployment/offline.md +++ b/content/docs/observability/deployment/offline.md @@ -8,6 +8,11 @@ description: > The following instructions can be followed when a Helm chart will be installed in an environment that does not have an internet connection and will be unable to download the Helm chart and related Docker images. +## Prerequisites + +- Helm 3.3 +- The deployment of one or more [supported](../#supported-csi-drivers) Dell CSI drivers + ### Dependencies Multiple Linux-based systems may be required to create and process an offline bundle for use. diff --git a/content/docs/observability/deployment/online.md b/content/docs/observability/deployment/online.md index 87ab82b411..8c478f8751 100644 --- a/content/docs/observability/deployment/online.md +++ b/content/docs/observability/deployment/online.md @@ -33,6 +33,11 @@ If the Authorization module is enabled for the CSI drivers installed in the same - Verifies the appropriate Secrets and ConfigMap exist in the CSI driver namespace. - Updates the CSM for Observability deployment to use the existing Authorization instance if not already enabled during the initial installation of CSM for Observability. +## Prerequisites + +- Helm 3.3 +- The deployment of one or more [supported](../#supported-csi-drivers) Dell CSI drivers + ## Online Installer The following instructions can be followed to install CSM for Observability in an environment that has an internet connection and is capable of downloading the required Helm chart and Docker images. From 6faa19b59c84201ef9c77bfac1a24b1d78189692 Mon Sep 17 00:00:00 2001 From: Shayna Finocchiaro <66699024+shaynafinocchiaro@users.noreply.github.com> Date: Tue, 15 Feb 2022 14:42:21 -0500 Subject: [PATCH 4/5] updates to prometheus docs --- content/docs/observability/deployment/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/observability/deployment/_index.md b/content/docs/observability/deployment/_index.md index 321c8d687a..03c6289614 100644 --- a/content/docs/observability/deployment/_index.md +++ b/content/docs/observability/deployment/_index.md @@ -25,7 +25,7 @@ These components must be deployed according to the specifications defined below. ### Prometheus -The Prometheus service should be running on the same Kubernetes cluster as the CSM for Observability services. As part of the CSM for Observability deployment, the OpenTelemetry Collector gets deployed. The OpenTelemetry Collector is what CSM for Observability pushes metrics so that the metrics can be consumed by Prometheus. This means that Prometheus must be configured to scrape the metrics data from the OpenTelemetry Collector. +The Prometheus service should be running on the same Kubernetes cluster as the CSM for Observability services. As part of the CSM for Observability deployment, the OpenTelemetry Collector gets deployed. CSM for Observability pushes metrics to the OpenTelemetry Collector where the metrics are consumed by Prometheus. Prometheus must be configured to scrape the metrics data from the OpenTelemetry Collector. | Supported Version | Image | Helm Chart | | ----------------- | ----------------------- | ------------------------------------------------------------ | @@ -33,7 +33,7 @@ The Prometheus service should be running on the same Kubernetes cluster as the C **Note**: It is the user's responsibility to provide persistent storage for Prometheus if they want to preserve historical data. -#### Prometheus Deployment +#### Prometheus Helm Deployment Here is a sample minimal configuration for Prometheus. Please note that the configuration below uses insecure skip verify. If you wish to properly configure TLS, you will need to provide a ca_file in the Prometheus configuration. The certificate provided as part of the CSM for Observability deployment should be signed by this same CA. For more information about Prometheus configuration, see [Prometheus configuration](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#configuration). @@ -111,7 +111,7 @@ Here is a sample minimal configuration for Prometheus. Please note that the conf On your terminal, run the command below: ```terminal - helm install prometheus prometheus-community/prometheus -n [CSM_NAMESPACE] --create-namespace -f prometheus-values.yaml + helm install prometheus prometheus-community/prometheus -n [CSM_NAMESPACE] -f prometheus-values.yaml ``` ### Grafana From f6aebfaf3bd331f87c68273c94fcb921e255dfa0 Mon Sep 17 00:00:00 2001 From: Shayna Finocchiaro <66699024+shaynafinocchiaro@users.noreply.github.com> Date: Thu, 17 Feb 2022 09:26:23 -0500 Subject: [PATCH 5/5] link to additional deployment methods --- content/docs/observability/deployment/_index.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/content/docs/observability/deployment/_index.md b/content/docs/observability/deployment/_index.md index 03c6289614..4f4eaf5877 100644 --- a/content/docs/observability/deployment/_index.md +++ b/content/docs/observability/deployment/_index.md @@ -18,8 +18,9 @@ The following third-party components are required in the same Kubernetes cluster * [Prometheus](#prometheus) * [Grafana](#grafana) +* [Other Deployment Methods](#other-deployment-methods) -These components must be deployed according to the specifications defined below. +There are various ways to deploy these components. We recommend following the Helm deployments according to the specifications defined below. **Tip**: CSM for Observability must be deployed first. Once the module has been deployed, you can proceed to deploying/configuring Prometheus and Grafana. @@ -150,7 +151,7 @@ Settings for the Grafana SimpleJson data source: | With CA Cert | Enabled (If using CA certificate) | -#### Grafana Deployment +#### Grafana Helm Deployment Below are the steps to deploy a new Grafana instance into your Kubernetes cluster: @@ -267,6 +268,11 @@ Below are the steps to deploy a new Grafana instance into your Kubernetes cluste helm install grafana grafana/grafana -n [CSM_NAMESPACE] -f grafana-values.yaml ``` +### Other Deployment Methods + +- [Grafana Labs Operator Deployment](https://grafana.com/docs/grafana-cloud/kubernetes/prometheus/prometheus_operator/) +- [Rancher Monitoring and Alerting Deployment](https://rancher.com/docs/rancher/v2.6/en/monitoring-alerting/) + ## Importing CSM for Observability Dashboards Once Grafana is properly configured, you can import the pre-built observability dashboards. Log into Grafana and click the + icon in the side menu. Then click Import. From here you can upload the JSON files or paste the JSON text directly into the text area. Below are the locations of the dashboards that can be imported: