All Products
Search
Document Center

Simple Log Service:Install Simple Log Service Kibana on Microsoft Azure by using Helm charts

Last Updated:Mar 02, 2026

This topic describes how to install Simple Log Service Kibana by using Helm charts in multicloud scenarios. On Microsoft Azure, you can install a Helm chart named sls-kibana by using Helm tools to run a log analysis and visualization system, which includes Kibana and related components. This topic describes how to build a log analysis system on Microsoft Azure.

Procedure

If you use an Alibaba Cloud Container Service for Kubernetes (ACK) environment, perform operations by following the instructions provided in Connect Simple Log Service to Kibana.

  1. Create and modify the values.yaml file. The following sample code shows the content of the file. Change the parameter values based on your business requirements.

    kibana:
      serviceType: ClusterIP # The type of the service. Valid values: ClusterIP and LoadBalancer.
    #  serviceAnnotation: # The annotation of the service.
    #    service.beta.kubernetes.io/azure-load-balancer-internal: 'true'
    #    service.beta.kubernetes.io/azure-load-balancer-internal-subnet: "xxx-subnet"
      ingressClass: nginx # Change the value based on the Ingress controller that you install. If this parameter is left empty, Ingress is not used.
      ingressDomain: # You can leave this parameter empty. If you want to access Kibana by using a domain name, configure this parameter.
      ingressPath: /kibana/ # Required. The subpath that is used to access Kibana.
      # If you configure the ingressDomain parameter, you can set the ingressPath parameter to /.
    #i18nLocale: en # The language of Kibana. Default value: en. If you want to use Chinese, you can set the value to zh-CN.
    
    elasticsearch:
      password: aStrongPass  # Change the password of the Elasticsearch cluster based on your business requirements. You can use the password to log on to the Kibana console. The username that is used to access the Elasticsearch cluster is elastic.
      diskStorageSize: 16Gi
      diskStorageClassName: managed-csi # The name of the StorageClass.
    
    repository:
      region: cn-hangzhou
      # The region where the image resides. If the image resides in a region in the Chinese mainland, set the value to cn-hangzhou. If the image resides in a region outside the Chinese mainland, set the value to ap-southeast-1. The image is pulled over the Internet.
    
    sls:
      - project: k8s-log-c5****** # The Simple Log Service project.
        endpoint: cn-huhehaote.log.aliyuncs.com # The endpoint of the Simple Log Service project.
        accessKeyId: The AccessKey ID that is used to access Simple Log Service.
        accessKeySecret: The AccessKey secret that is used to access Simple Log Service.
      #  alias: etl-logs # Optional. If the name of the Simple Log Service project specified by the project parameter is excessively long in Kibana, you can configure this parameter to specify an alias for the project.
      #  kibanaSpace: default  # Optional. The space in which the index pattern is created. If no space exists, a space is automatically created.
      #  logstoreFilters: "*" # Optional. The Logstores that are used to automatically create index patterns. Separate multiple index patterns with commas (,) and enclose index patterns in double quotation marks (""). Example: "access*,error*".
    
      # If you want to specify another Simple Log Service project, follow the preceding steps.
      #- project: etl-dev2 # The Simple Log Service project.
      #  endpoint: cn-huhehaote.log.aliyuncs.com # The endpoint of the Simple Log Service project.
      #  accessKeyId: The AccessKey ID that is used to access Simple Log Service.
      #  accessKeySecret: The AccessKey secret that is used to access Simple Log Service.
      #  alias: etl-logs2 # Optional. If the name of the Simple Log Service project specified by the project parameter is excessively long in Kibana, you can configure this parameter to specify an alias for the project.
      #  kibanaSpace: default  # Optional. The space in which the index pattern is created. If no space exists, a space is automatically created.
      #  logstoreFilters: "*" # Optional. The Logstores that are used to automatically create index patterns. Separate multiple index patterns with commas (,) and enclose index patterns in double quotation marks (""). Example: "access*,error*".
    
    #kproxy:
    #  maxAllowTimeRangeSeconds: 900 # The time range that is allowed to query data. By default, no limits are imposed on time ranges.

    Parameter

    Description

    kibana.ingressClass

    The class of the Ingress controller. Specify the value based on the Ingress controller installed. For more information, see Manage components. Valid values:

    • ALB Ingress Controller: Set the value to alb.

    • MSE Ingress Controller: Set the value to mse.

    • NGINX Ingress Controller: Set the value to nginx.

    kibana.ingressDomain

    The domain name used to access Kibana. You can leave this parameter empty. If you want to access Kibana by using a domain name, configure this parameter.

    repository.region

    The region where the image resides. If the image resides in a region in the Chinese mainland, set the value to cn-hangzhou. If the image resides in a region outside the Chinese mainland, set the value to ap-southeast-1. The image is pulled over the Internet.

    kibana.ingressPath

    The subpath used to access Kibana. If you configure the ingressDomain parameter, set the ingressPath parameter to /.

    elasticsearch.password

    The password of the Elasticsearch cluster. Change the password as needed. Use this parameter to log on to the Kibana console. The username used to access the Elasticsearch cluster is elastic.

    kproxy.ecsRoleName

    ECS instance RAM role. For the permissions required for the RAM role, see RAM authorization.

    sls.project

    The name of the SLS project. For more information, see Manage projects.

    sls.endpoint

    The endpoint of the SLS project. For more information, see Manage projects.

    sls.accessKeyId

    The AccessKey ID created for the RAM user. The RAM user must have the required permissions to query logs in the logstore. For more information, see Grant permissions to a RAM user.

    sls.accessKeySecret

    The AccessKey secret created for the RAM user. The RAM user must have the required permissions to query logs in the logstore. For more information, see Grant permissions to a RAM user.

    sls.alias

    Optional. If the name of the SLS project specified by the sls.project parameter is excessively long in Kibana, you can configure this parameter to specify an alias for the project.

    sls.kibanaSpace

    Optional. The space in which the index pattern is created. If no space exists, a space is automatically created.

    sls.logstoreFilters

    Optional. The logstores used to automatically create index patterns. Separate multiple index patterns with commas (,) and enclose index patterns in double quotation marks (""). Example: "access*,error*".

  2. Create a namespace.

    kubectl create namespace sls-kibana
  3. Run the installation command.

    helm install sls-kibana \
     https://sls-kproxy.oss-cn-hangzhou.aliyuncs.com/sls-kibana-1.5.5.tgz \
      -f values.yaml --namespace sls-kibana

FAQ

How do I uninstall Helm?

helm uninstall sls-kibana --namespace sls-kibana

How do I display high-precision timestamps in Kibana?

  1. To ensure that logs that have high-precision time values are collected to SLS, you must configure timestamps accurate to the nanosecond. For more information, see Collect logs whose timestamps are accurate to the nanosecond.

  2. Add the indexes of the __time_ns_part__ field whose data type is long to field indexes. Specific Kibana query statements may be converted to SQL statements for execution. In this case, you must include high-precision time values in the SQL results.

How do I update a Helm chart?

The process in which a Helm chart is updated is similar to the process in which a Helm chart is installed. Simply change the helm install command to the helm upgrade command. You can use the values.yaml file used for Helm chart installation in the update process.

helm upgrade sls-kibana https://sls-kproxy.oss-cn-hangzhou.aliyuncs.com/sls-kibana-1.5.5.tgz -f values.yaml --namespace sls-kibana