Feature: Remove CVE from image-scanner logs

[Neha130]

🔖 Feature description

The current implementation of the image-scanner logs includes CVE entries that are cluttering the logs and making it difficult to extract meaningful information. We propose a modification to exclude CVE entries from the logs to enhance clarity and usability.

🎤 Pitch / Usecases

Improve Log Clarity by Excluding CVE Entries

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[RajeevRanjan27]

@Neha130 Can you please add more info specifying how you have encountred this issue, and from which version of image scan you been using during this issue encountered?

If possible mention the api that cause the log scattered (if it is from orch side)

Please mention any flag you were using during the use of this feature...
You got those logs during the both versions (if yes please add these details)?

[Neha130]

@RajeevRanjan27 This is a simple feature request to refactor image scanner logging by not printing CVEs while image scan is happening in any application.
How can you visualise this ? ->

• enable image scan
• trigger CI
• View image scanner's live logs and check for CVEs getting printed in logs

Now we don't want those CVEs to be printed in Image Scanner logs as it gets printed in a single line which is extensively big in certain scenarios if number of vulnerabilities are quite high in any application. This makes it extremely difficult for us to debug issues from logs. Another issue is that fluent bit which is a log shipper component crashes multiple times across multiple enterprises while parsing image scanner logs.

Please mention any flag you were using during the use of this feature... -> NA
ou got those logs during the both versions (if yes please add these details)? -> v1 yes, not sure about v2

[RajeevRanjan27]

thanks for the info.. looking into it.