Skip to content

[VMware vSphere]: Date parsing error for login events when missing AM/PM #13865

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
georgessamaha opened this issue May 9, 2025 · 0 comments
Labels
Integration:vsphere VMware vSphere needs:triage Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]

Comments

@georgessamaha
Copy link

georgessamaha commented May 9, 2025

Integration Name

VMware vSphere [vsphere]

Dataset Name

vsphere.log

Integration Version

1.18.2

Agent Version

8.18

OS Version and Architecture

Ubuntu 20.04 LTS

User Goal

Issue: Data processor is failing when we get the date as Wednesday, 16 April, 2025 11:10:33 in the VMware logs.

Parent Ingest Pipeline: logs-vsphere.log-1.18.2

Child Ingest Pipeline: logs-vsphere.log-1.18.2-login

Processor: date

{
    "date": {
      "formats": [
        "EEEE, dd MMMM, yyyy hh:mm:ss a" ],
      "field": "event.start",
      "target_field": "event.start",
      "if": "ctx.event?.start != null"
    }
  }

Event Original : Wednesday, 16 April, 2025 11:10:33 (Only Date timestamp field is providing)

Error Message:: error.message Text 'Wednesday, 16 April, 2025 11:10:33' could not be parsed at index 34
Root cause analysis: The Current processor is expecting the date with am/pm. Due to this it is failing when we get date without am/pm in the logs.

Existing Features

The Current date processor in logs-vsphere.log-1.18.2-login is expecting the date with am/pm. Due to this it is failing when we get date without am/pm in the logs.

What did you see?

Sample log:
2025-04-24T09:29:25.236Z INFO websso[74:tomcat-http--36] [CorId=6ae8edc4-79bb-4d1a-9230-4b51ffbe772a] [auditlogger] {\"user\":\"[email protected]\",\"client\":\"10.15.96.14\",\"timestamp\":\"04/24/2025 09:29:25 GMT\",\"description\":\"User [email protected]@10.15.96.14 logged in with response code 200\",\"eventSeverity\":\"INFO\",\"type\":\"com.vmware.sso.LoginSuccess\"}

The data parsing error is the one inside the message, not the syslog header:
"timestamp":"04/24/2025 09:29:25 GMT\

Anything else?

No response

@georgessamaha georgessamaha changed the title [Integration Name]: Brief description of the feature [Vsphere - vmware]: Date parsing error for login events when missing AM/PM May 9, 2025
@georgessamaha georgessamaha changed the title [Vsphere - vmware]: Date parsing error for login events when missing AM/PM [VMware vSphere]: Date parsing error for login events when missing AM/PM May 9, 2025
@andrewkroh andrewkroh added Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] Integration:vsphere VMware vSphere labels May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Integration:vsphere VMware vSphere needs:triage Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]
Projects
None yet
Development

No branches or pull requests

2 participants