Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-8007

Mark logType for azureMonitor output as required field in ClusterLogForwarder CRD

XMLWordPrintable

    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • NEW
    • Bug Fix
    • Logging - Sprint 279, Logging - Sprint 280
    • Moderate

      Description of problem:

      Currently, the parameter logType in ClusterLogForwarder's azureMonitor output config is not marked as a "required" config.

      Not configuring logType for azureMonitor output configĀ  causes vector pods to crash.

      Version-Release number of selected component (if applicable):

      RHOL 6.4

      How reproducible:

      100%

      Steps to Reproduce:

      1. Create a ClusterLogForwarder to send logs to Azure Log Analytics
      2. Do not use logType in the azureMonitor output config
      3. The vector pods crashes with below error
      Creating the directory used for persisting Vector state /var/lib/vector/openshift-logging/test
      Starting Vector process...
      2025-10-24T08:42:56.862842Z ERROR vector::topology::builder: Configuration error. error=Sink "output_abc_azure": invalid log_type "": log type can only contain letters, numbers, and underscore (_), and may not exceed 100 characters 

      Actual results:

      The collector pods crash with above error when logType is not configured.

      Expected results:

      logType config in ClusterLogForwarder output needs to be marked as "required" config.

      Additional info:

              vparfono Vitalii Parfonov
              rhn-support-dgautam Dhruv Gautam
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: