Getting Data In

logs with no timestamp automatically show +15 hrs of time stamp

KulvinderSingh
Path Finder

"CEF:0|Bitdefender|GravityZone|6.35.1-1|35|Product Modules Status|5|BitdefenderGZModule=modules dvchost=xxx      BitdefenderGZComputerFQDN=xxxxx dvc=x.x.x.x deviceExternalId=xxxxx BitdefenderGZIsContainerHost=0 BitdefenderGZMalwareModuleStatus=enabled BitdefenderGZBehavioralScanAVCModuleStatus=enabled BitdefenderGZDataLossPreventionModuleStatus=disabled"

 

The logs are from Bitdefender and they show a time diff of +15 hrs. and there is no timestamp in logs no other source types from same HF show the behavior only bit-defender logs. All the help is appreciated to correct the time.

Labels (4)
0 Karma
1 Solution

KulvinderSingh
Path Finder

It was an issue with NTP sync on the servers got it corrected and its fine now.

View solution in original post

0 Karma

KulvinderSingh
Path Finder

It was an issue with NTP sync on the servers got it corrected and its fine now.

0 Karma

PickleRick
SplunkTrust
SplunkTrust

1. Check the sourcetype props

2. CEF typically comes with a syslog header. You're not showing the header - maybe it's been cut after the time had beed parsed out from it.

It all boils down to verifying:

1) Raw format of the data coming from the source with tcpdump to be sure what's on the wire

2) Settings for the sourcetype - how the timestamp is being parsed/assigned and how the event is modified on ingestion.

0 Karma

KulvinderSingh
Path Finder

Thanks @PickleRick let me check will update.

0 Karma
Get Updates on the Splunk Community!

Enter the Dashboard Challenge and Watch the .conf24 Global Broadcast!

The Splunk Community Dashboard Challenge is still happening, and it's not too late to enter for the week of ...

Join Us at the Builder Bar at .conf24 – Empowering Innovation and Collaboration

What is the Builder Bar? The Builder Bar is more than just a place; it's a hub of creativity, collaboration, ...

Combine Multiline Logs into a Single Event with SOCK - a Guide for Advanced Users

This article is the continuation of the “Combine multiline logs into a single event with SOCK - a step-by-step ...