# airec-logging

Part of **AIREC**

# AIRec Logging and Monitoring Console Guide

## Operations Overview

| Operation | Console Entry Path | Prerequisites | Description |
|----------|-------------------|--------------|-------------|
| Change Kibana Language | Products > Product List > Apsara Stack O&M > Apsara Infrastructure Management Framework | - The URL of the Apsara Stack Operations console is obtained<br>- Google Chrome browser is recommended<br>- logservicelite-elk has reached the desired state | Switch the Kibana monitoring interface display language from Chinese to English by editing the i18n.locale setting in the configuration file. |

## Operation Steps

### Change Kibana Language

**Navigation**: Products > Product List > Apsara Stack O&M > Apsara Infrastructure Management Framework

**Prerequisites**:
- The URL of the Apsara Stack Operations console is obtained
- Google Chrome browser is recommended
- logservicelite-elk has reached the desired state

1. Log on to the Apsara Infrastructure Management Framework and locate the machine hosting the Kibana container.
   - Element: **Products** (menu) — left-side navigation pane

2. Navigate to the Apsara Stack O&M section.
   - Element: **Apsara Stack O&M** (link) — Product List page

3. Access the Apsara Infrastructure Management Framework.
   - Element: **Apsara Infrastructure Management Framework** (link) — Product List page

4. Go to Cluster Operations and select the tianji cluster.
   - Element: **Operations > Cluster Operations** (menu) — left-side navigation pane

5. Find the logservicelite-elk service and click its name.
   - Element: **logservicelite-elk** (link) — Services tab of Cluster Details

6. Click the logservicelite-elk.Kibana# server role to access TerminalService.
   - Element: **logservicelite-elk.Kibana#** (link) — machine list, Actions column
   - Notes: A **Terminal** button appears in the Actions column after selection.

7. Open a terminal session to the target machine.
   - Element: **Terminal** (button) — left-side navigation pane
   - Notes: A machine selection interface appears; proceed to connect.

8. Retrieve the Kibana container ID using the Docker command.
   - Element: **sudo docker ps \|grep ogservicelite-elk.Kibana__.kibana** (text_input) — Terminal
   - Notes: Example output shows the running container ID. Copy this ID for the next step.

9. Enter the Kibana container using the retrieved container ID.
   - Element: **sudo docker exec -it \<docker_id\> bash** (text_input) — Terminal
   - Notes: Replace `<docker_id>` with the actual container ID from Step 8.

10. Edit the Kibana configuration file to change the language setting.
    - Element: **vi /home/admin/kibana/config/kibana.yml.tpl** (text_input) — Terminal
    - Notes: Locate the line `i18n.locale: "zh-CN"` and change it to `i18n.locale: "en"`. Save and exit using `:wq`.

11. Exit the container and restart it to apply the changes.
    - Element: **exit** (text_input) — Terminal
    - Notes: After exiting, run `sudo docker restart <docker_id>` (replace `<docker_id>` with the container ID). The Kibana interface will reload in English after restart.

## FAQ

Q: Where can I find the Kibana service in the console?
A: Navigate to Products > Product List > Apsara Stack O&M > Apsara Infrastructure Management Framework, then go to Cluster Operations > tianji cluster > Services tab, and look for **logservicelite-elk**.

Q: Do I need special permissions to access TerminalService?
A: Yes, you must have administrative or O&M permissions in the Apsara Infrastructure Management Framework to access TerminalService and execute Docker commands.

Q: What happens if I forget to add double quotes around "en" in the kibana.yml.tpl file?
A: Kibana may fail to start or revert to the default language. Always ensure the value is written as `i18n.locale: "en"` with double quotes.

Q: Can I change the language back to Chinese later?
A: Yes, simply edit the same file again and set `i18n.locale: "zh-CN"`, then restart the container.

Q: Is it necessary to restart the container after changing the configuration?
A: Yes. The configuration is only loaded at startup, so a restart via `sudo docker restart <docker_id>` is required for the language change to take effect.

## Pricing & Billing

### Billing Model
Free

### Free Tier
No specific pricing mentioned; assumed free as part of cloud product.

### Billing Notes
No billing-related information provided.