-
Bug
-
Resolution: Unresolved
-
Major
-
Logging 6.1.0
-
False
-
None
-
False
-
NEW
-
NEW
-
Before this update, when infrastructure namespaces were included in application inputs, the `log_type` was set as `application`. With this update, the `log_type` of infrastructure namespaces included in application inputs is set to `infrastructure`.
-
Bug Fix
-
-
-
Log Collection - Sprint 262
Description of problem:
When infrastructure namespaces are included under `Application` inputs, their log_type is set to application instead of infrastructure.
Example when using `openshift*`, logs from namespace `openshift-logging` have a log_type set to application.
Version-Release number of selected component (if applicable):
5.9, 6.0, 61
How reproducible: Always
Steps to Reproduce:
- Create CLF with application input that includes `openshift*`
apiVersion: observability.openshift.io/v1 kind: ClusterLogForwarder metadata: name: clf-71488 namespace: e2e-test-vector-cw-pknkn spec: inputs: - application: includes: - namespace: openshift* name: new-app type: application managementState: Managed outputs: - cloudwatch: authentication: iamRole: roleARN: key: role_arn secretName: clf-71448 token: from: serviceAccount type: iamRole groupName: logging-71488-ci-op-1wxtsnq8-77988-wqmt4. {.log_type||"none-typed-logs"} region: ap-northeast-1 tuning: {} name: cloudwatch type: cloudwatch pipelines: - inputRefs: - new-app name: to-cloudwatch outputRefs: - cloudwatch serviceAccount: name: clf-71448
- Query logs and check log_type
Actual results:
log_type of infrastructure namespace logs are set to `application`
Expected results:
log_type of infrastructure namespace logs are set to `infrastructure`
- clones
-
LOG-6354 [Logging 6.0.z] Infra namespaces spec'd as app inputs have log_type set to 'application'
- Closed
- links to