Skip to content

Integrations that parse timestamps without a year fail after new year #4950

@jsoriano

Description

@jsoriano

Some integrations have started failing after the change of year. These integrations are likely parsing timestamps without a year.

These tests should be fixed by checking first if the year is actually not found in the logs, or if there is some parsing issue.

You can find the failing packages for example in these builds:

Pinging owners of affected packages: @elastic/security-external-integrations @elastic/obs-service-integrations @elastic/elastic-agent-data-plane

cc @elastic/ecosystem

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions