Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Re: Why does the date format in scheduled csv repo...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have made a scheduled report which emails a csv file containing counts of particular events for each day in the last seven days.
The format looks a little like this:
Date - X, Y, Z
2019-08-12 - 5, 6, 8
2019-08-13 - 10, 8, 7
2019-08-14 - 2, 1, 1
The output in the Splunk UI shows dates correctly ( | fieldformat Date= strftime(Date, "%Y-%m-%d" ), and when I download a CSV report manually the dates also look fine.
However, in the scheduled report sent via email, dates are presented as below:
Date
1565532000
1565618400
1565704800
1565791200
1565877600
1565964000
1566050400
Any thoughts on what's going on here?
Thanks!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The actual data is still an integer. Generally you should be using fieldformat the way that you are, but if the output is going to be exported and you need human-readable dates, then swap fieldformat for eval like this:
... | eval Date=strftime(Date, "%Y-%m-%d")
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The actual data is still an integer. Generally you should be using fieldformat the way that you are, but if the output is going to be exported and you need human-readable dates, then swap fieldformat for eval like this:
... | eval Date=strftime(Date, "%Y-%m-%d")
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, will see how it goes!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Come back and let us know how it went and click Accept to close the question.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Announcing Modern Navigation: A New Era of Splunk User Experience
Modernize your Splunk Apps – Introducing Python 3.13 in Splunk
Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...
