Enabling Elastic monitoring

Elasticsearch monitoring is a free Elastic X-Pack feature that provides operational visibility. Starting with IBM Cloud Private 3.2.1, this feature is enabled during logging service installation in both managed and standard modes. You can use these instructions to disable the Elastic monitoring feature for both mode types.

Before you begin, consider the following tips:

No action needed to turn Elastic monitoring on since this feature is enabled by default.
By default, 7 days of Elastic health data is kept. To modify the default, follow the instructions in Update Data Retention Policy .
Elastic health metrics start to accumulate after the monitoring feature is turned on.
You can view the Elastic cluster health dashboard and metrics. From the Kibana web UI, select Monitoring from navigation menu.
Helm release name, logging is used in these instructions. If you use a different release name in standard mode, replace the name with the logging release name.

Extract the existing logging chart parameters.
- Extract Helm parameters by running the following command: helm get values logging --tls > values-old.yaml
- Optionally, apply prior adjustments. All Kubernetes resource manifest adjustments that are made by using the kubectl command are overridden with values that are defined in chart parameters. Replica count, JVM heap size, or container memory limits are a few examples. If prior Kubernetes resource manifests were adjusted, make sure that you apply the same adjustments to values-old.yaml.
Prepare chart parameters.
- Create a values-override.yaml file to include the following parameters:
```
 xpack:
   monitoring: false
```
Download the chart.
- Identify chart version.
  
  Logging chart versions vary based on the installed IBM Cloud Private version. You can use IBM Cloud Private management console to find chart versions in the service catalog. The logging chart can be identified by the name ibm-icplogging under the mgmt-repo repository. You can also select SOURCE & TAR FILES from the IBM Cloud Private management console to find a local link to a chart.
- Download the chart .tar file.
  
  Run the following command by using the local link found in Step 3:
```
 curl -k https://<master ip>:8443/mgmt-repo/requiredAssets/ibm-icplogging-x.y.z.tgz > ibm-icplogging-x.y.z.tgz
```

Upgrade the Helm chart.

Run the following command. Replace x.y.z with the version that you found in Step 3:

helm upgrade logging ibm-icplogging-x.y.z.tgz -f values-old.yaml -f values-override.yaml --recreate-pods --force --timeout 600 --tls

The logging service becomes available in approximately 5 - 10 minutes. You can also check Helm upgrade status by using the following command:
```
 helm history --tls logging
```