[BUG] Trivy log events are a different format to other agent logs

[lewis-jackson-bots]

I've enabled container image scanning on the DataDog agent installed via Helm by setting:

datadog:
  # Software Bill of Materials configuration
  sbom:
    containerImage:
      # datadog.sbom.containerImage.enabled -- Enable SBOM collection for container images
      enabled: true

      # datadog.sbom.containerImage.uncompressedLayersSupport -- Use container runtime snapshotter
      # This should be set to true when using EKS, GKE or if containerd is configured to
      # discard uncompressed layers.
      # This feature will cause the SYS_ADMIN capability to be added to the Agent container.
      uncompressedLayersSupport: false

  containerImageCollection:
    # datadog.containerImageCollection.enabled -- Enable collection of container image metadata

    # This parameter requires Agent version 7.46+
    enabled: true

We now get log events that look like this:

2024-08-02T13:44:39.122Z	�[33mWARN�[0m	No OS package is detected. Make sure you haven't deleted any files that contain information about the installed packages.

Here is an example of these logs below some other DataDog agent logs where the different log format and colourisation/colorization can be observed:

In our DataDog log pipeline these are not parsed correctly and the log level is interpreted as ERROR rather than the expected level WARN.

The source of this log event appears to be from the DataDog fork of Trivy here: https://github.com/DataDog/trivy/blob/e2dfee208fe30a395cb9819c9fce03b0b7c0ae24/pkg/scanner/local/scan.go#L99

Agent Environment
Agent version: v7.55.2
Image tag: gcr.io/datadoghq/agent:7.55.2

Describe what happened:

Log events are output by the Trivy package which don't match the format of the datadog-agent events.

Describe what you expected:

Log events should be parseable using the same pipeline as other datadog-agent events.

Steps to reproduce the issue:

• Install the agent with container image scanning enabled
• Scan an image with a busybox base to trigger the No OS package is detected. event
• The log event is output without | separators and with colours.

Additional environment details (Operating System, Cloud provider, etc):

AKS Kubernetes, installed via Helm with chart version 3.69.3.