Loading...

XML

Word

Printable

Details

Type: Story
Resolution: Done
Priority: Blocker
Fix Version/s: Pipelines 1.11.0
Affects Version/s: None
Component/s: Pipelines as Code
Labels:
- 2023Q2

Story Points:
1
Epic Link:
Pipelines as Code, Split Logging By Namespace
Blocked:
False
Blocked Reason:
None
Ready:
False
Release Note Text:

Hide
Today PAC emits logs without the namespace information which leads to difficulty in debugging logs when there are Repos created in 1000s of namespaces

This changes will add Namespace info to each logs and make easier to grep logs or forward logs based on Namespace information

https://user-images.githubusercontent.com/9441662/234328409-e544ba5b-1463-4de8-8df2-db2fea6f2a00.png

Show
Today PAC emits logs without the namespace information which leads to difficulty in debugging logs when there are Repos created in 1000s of namespaces This changes will add Namespace info to each logs and make easier to grep logs or forward logs based on Namespace information https://user-images.githubusercontent.com/9441662/234328409-e544ba5b-1463-4de8-8df2-db2fea6f2a00.png
Git Pull Request:
https://github.com/openshift-pipelines/pipelines-as-code/pull/1251

Sprint:
Pipelines Sprint 236, Pipelines Sprint 237, Pipelines Sprint 238, Pipelines Sprint 239

SFDC Cases Counter:
SFDC Cases Links:

Description

Current Scenario:

PAC uses EmitMessage function to emit the logs but there is no info related to namespace

Expected Scenario:

PAC should include namespace info in the logs of controller

Attachments

Activity

People

Assignee:: Savita .

Reporter:: Savita .

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2023/04/18 10:45 AM

Updated:: 2024/03/11 11:12 AM

Resolved:: 2023/06/01 8:08 AM