Deployment Architecture

time indexing not correct

splunksurekha
Path Finder

alt text

Hi attached is the image which shows there is a difference in the Time field and the actual time which comes from the input file getting indexed with column name alertdate.
so that means the index time and alertdate are not in sync which is incorrect right . Can you help me here.

I am using below configuration.
props.conf
[zbxAlertReport]
SHOULD_LINEMERGE = false
INDEXED_EXTRACTIONS = csv
FIELD_DELIMITER = ,
FIELD_NAMES = alerthost,hostname,alertname,alertstatus,alertseverity,alertdate
TIMESTAMP_FIELDS = date
TIME_FORMAT = %a%b%d%H:%M:%S%Y
category = Structured
MAX_TIMESTAMP_LOOKAHEAD = 500

transforms.conf
[zbxAlertReport]
filename = ZbxDailyReport.csv

Tags (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Splunk isn't finding a timestamp that matches the specified criteria so it's using current time. Making the following changes should fix it.

The TIMESTAMP_FIELDS value is "date", but there is no such field in the event. Perhaps it should be "alertdate".
The TIME_FORMAT value looks like it doesn't match the data in the alertdate field. Try TIME_FORMAT = %a %b %d %H:%M:%S %Y.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...