Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Getting Data In
×
Are you a member of the Splunk Community?
Sign in or Register with your Splunk account to get your questions answered, access valuable resources and connect with experts!
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- How to extract timestamps with milliseconds that h...
Options
- 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
yutaka1005
Builder
05-29-2019
02:14 AM
I have below logs.
Wed May 15 13:00:00.4 ... (*it is 4miliseconds)
Wed May 15 13:00:00.82 ... (*it is 82miliseconds)
Wed May 15 13:00:00.110 ... (*it is 110miliseconds)
But these logs's timestamp are extracted like below.
2019 5/15 13:00:00.400 ... (*actually, it is 4miliseconds)
2019 5/15 13:00:00.820 ... (*actually, it is 82miliseconds)
2019 5/15 13:00:00.110 ... (*actually, it is 110miliseconds)
Is there workaround to extract such timestamps in right way?
If someone know about it, please tell me.
Thank you.
1 Solution
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
woodcock
Esteemed Legend
05-29-2019
08:26 AM
The problem is actually in how milliseconds work, not in how Splunk works. For your examples:
Wed May 15 13:00:00.4 ... (*it is 400 miliseconds)
Wed May 15 13:00:00.82 ... (*it is 820 miliseconds)
Wed May 15 13:00:00.110 ... (*it is 110 miliseconds)
Going the other way:
Wed May 15 13:00:00.004 ... (*it is 4 miliseconds)
Wed May 15 13:00:00.082 ... (*it is 82 miliseconds)
Wed May 15 13:00:00.110 ... (*it is 110 miliseconds)
So almost certainly everything is A-OK.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
woodcock
Esteemed Legend
05-29-2019
08:26 AM
The problem is actually in how milliseconds work, not in how Splunk works. For your examples:
Wed May 15 13:00:00.4 ... (*it is 400 miliseconds)
Wed May 15 13:00:00.82 ... (*it is 820 miliseconds)
Wed May 15 13:00:00.110 ... (*it is 110 miliseconds)
Going the other way:
Wed May 15 13:00:00.004 ... (*it is 4 miliseconds)
Wed May 15 13:00:00.082 ... (*it is 82 miliseconds)
Wed May 15 13:00:00.110 ... (*it is 110 miliseconds)
So almost certainly everything is A-OK.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
harsmarvania57
Ultra Champion
05-29-2019
03:06 AM
Is this timestamp from Database using DB Connect ?
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!
What Is Splunk? Here’s What You Can Do with Splunk
Hey Splunk Community, we know you know Splunk. You likely leverage its unparalleled ability to ingest, index, ...
Level Up Your .conf25: Splunk Arcade Comes to Boston
With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...
Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...
Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...
