# Unified logs report to track issues

ISD has a feature to collect all the service logs to identify the errors and resolve them with immediate effect by the OpsMx support team. ISD allows you to fetch all the service logs and this data needs to be collected and shared with OpsMx support teams for faster, more accurate, and more efficient support.

This feature helps you reduce the time to identify the issues and resolve them immediately. To enable this feature, the customer needs **Elasticsearch** to store and search your data and **kibana** to visualize and manage it. To do follow the instructions below.

### Prerequisites:

* Installed ISD

### Enable Central Logging in ISD 

1. To install ELK and kibana Central Logging needs to be enabled. Get the values.yaml file that is used for ISD installation and add **enablecentralLogging** in values.yaml parallel to the **global** section at the root level.<br>

   ```
   enableCentralLogging: true
   ```

   \
   Ref:<https://github.com/OpsMx/enterprise-spinnaker/blob/master/charts/oes/values.yaml#L1257>
2. Helm upgrade is required to reflect the change that is performed in the above step. Execute the command below to perform helm upgrade.<br>

   ```
    helm upgrade <release-name> . -f <values.yaml> -n <namespace> -timeout=6m
   ```

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong>: The release name and namespace should be the same which is used for ISD installation.</p></div>

   * Execute the following command to see the release name, namespace, revision version, deployment detail, chart version, and ISD version.<br>

     ```
     helm ls -n elk
     ```

### Access kibana

To view the unified log reports, kibana service needs to be accessed via port-forwarded and the user can generate the logs report as a CSV file. To do, follow the instructions below.

1. Execute the following command to access the kibana service via port-forwarded.<br>

   ```
   kubectl port-forward svc/<RELEASE_NAME>-kibana 8081:5601 -n NAMESPACE
   ```

   \
   Keep running, it shows messages such as "**Forwarding from 127.0.0.1:8081 -> 5601**”.<br>
2. Now open your browser and navigate to **<http://localhost:8081>** and kibana dashboard appears as below:<br>

   <figure><img src="https://lh5.googleusercontent.com/UGu9LV8s5rJ8iG9Vpr3f7WymVXjiUStYk53p1-tcsYcrdfOdlcqT-BA1X6EnxxJxJxBS4YfgMGy9yxxM-bkRAc897r_YpiRwjDh5nXDi74zTcT91QfRRMGQf4Z7yCf1eHYBsSWVzc1q4k2KHfJ82oig" alt=""><figcaption></figcaption></figure>
3. Click **Discover**, from the kibana dashboard main menu.<br>

   <figure><img src="https://lh4.googleusercontent.com/s0XKZCDXRLDtUa6aY7-LUgl6hN0dQMz9qAuBB_Ad7wLCrb74F-pLloHjC1PJ9gHYEfF1KlzC62LQGgujbVR9j16RB5cJ9FsxQFP8CjnAFjjhq9GsoRAMzY8DPJIdei3THdgqy1xOE-lnnFiRq8MNJaI" alt=""><figcaption></figcaption></figure>
4. Locate the fields below, and then add them from the list of Available fields.
   * kubernetes.container\_name
   * Kubernetes.namespace\_name
   * Kubernetes.pod\_name<br>

     <figure><img src="https://lh5.googleusercontent.com/737tOstXTNETqzcYkwVhWxuB4pf_4gcOR8zTjJowaqJ-k5zxndGx9jX40QDS5QmAE1DOZVI3vaTymDKkw7peJxiaV7xVBVARxs9n6NCGfouo6GiCo-abZOrEshIRM8_3cwyauq8vmtHjPWvBXRn1roQ" alt=""><figcaption></figcaption></figure>
5. When all three fields are added, the main screen displays as follows:<br>

   <figure><img src="https://lh3.googleusercontent.com/cZurY5mnqvHO3j0_bOqqm1vZu_EgWdl6yFmfLj3K1n13bOS2xH_gpLIVWKYGYUyIRfCk0OupCrBh5lba-hdW4PYT7ASTNApUYj604VwXTMuqM6SLKCjXtdGRkAsssTcZNSJ7mCLt4SIE4a-88_cDtA" alt=""><figcaption></figcaption></figure>
6. Search for logs of all pods running in the ISD namespace using the field below. Change the date as needed; it will be within the last 15 minutes by default.\
   \
   **kubernetes.namespace\_name: \<NAMESPACE>**<br>

   <figure><img src="https://lh4.googleusercontent.com/01uUnsWwwHQPATWRNnrk4S0XrCm00Ur97XU363rhjO4iXxcZa6l1H-ePsQOXwmII9qMjMLHAsHc1BQMlvB7q2MTyeAaGceg-aZoGHtQH4r7f8PzAZTpsKHZUBMxjrqpfbmT_uVhatfUmu2lo1zPkFQ" alt=""><figcaption></figcaption></figure>
7. Click on save and save with a Title. <br>

   <figure><img src="https://lh3.googleusercontent.com/wLQyhfkRj5hdphG9o6spItqqsZ44dSDVnJG20Re51K52v6R2o-8jcn9Me060vMgq8i9vi1TbT7pU7Auj4efBrCgOmv1MAPmvguhTCT2pfxixKM3GK_nElOcl-QMgr_WKowHDgN9kCsvxFnm7dGutag" alt=""><figcaption></figcaption></figure>
8. Click on **Share** and **Generate CSV** to generate a CSV report.<br>

   <figure><img src="https://lh5.googleusercontent.com/Q2Kse-Gpdd2Uda4ZmD-eg7RltiFdb0yd8BQQGuU0LcU_4KBLa8db9ojari0ZP3BWThyVsI8veeQSARfhEvnqnx8PluaUKMF9dVyKuXgPQKsJ1ISnRkHgyucejPkHrHvJ28KlYFh8d-Ck-nOE8QdJ8aU" alt=""><figcaption></figcaption></figure>

Share the downloaded CSV file with the OpsMx support team on request for troubleshooting an issue that is reported.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/user-guide/unified-logs-report-to-track-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.