Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-182

Istio/ServiceMesh envoy log file grows continuously and parameter like '--log_rotate_max_size' is not considered.

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • OSSM 1.0.7
    • None

      Issue:
      --------
      One of my customers redirect Istio Envoy access logs to a file, for this purpose they changed accessLogFile: "/etc/istio/proxy/envoy.log" this is working fine, now their concern is regarding the growing size of this file.

      The customer tried to add rotation parameters in istio-sidecar-injector ConfigMap, but envoy.log file size continues to grow anyway:

      • '--log_target /etc/istio/proxy/envoy.log'
      • '--log_rotate /etc/istio/proxy/envoy.log'
      • '--log_rotate_max_size 2'
      • '--log_rotate_max_age 0'
      • '--log_rotate_max_backups 0'

      Need to know why the parameter '--log_rotate_max_size 2' (2 MB) is not considered? The customer has shown the screenshot in which the file has grown upto 3.3M

      I checked the ConfigMap yaml configuration and the syntax for the above parameters is correct. The configuration has been picked up by the Deployment properly.

      Version:
      ------------
      OpenShift 4.3.5
      OpenShift ServiceMesh 1.0.7

      Additional info:
      ------------
      I have Checked below Istio documentation and the parameters that are used as correct.

      https://istio.io/docs/ops/diagnostic-tools/component-logging/#log-rotation

      https://istio.io/pt-br/docs/reference/commands/sidecar-injector/

            rhn-support-nchavan Niket Chavan (Inactive)
            rhn-support-nchavan Niket Chavan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: