Dashboards & Visualizations

Not able to get Date in proper format when put in Visualization

aditsss
Motivator

Hi Everyone,

I am using below query:

index=abc ns=uio app_nameapi "ARC EVENT RECEIVED FROM SOURCE"| rex "RID:(?<RID>(\w+-){4}\w+)-(?<sourceagent>\w+-\w+)"|timechart count(RID) as "RID" by sourceagent

when I put it in line chart I am getting dates like this:

Tue March 2

Wed March 3

I want it all in proper date format.

In statics its coming in date format but when I put in line chart . Not getting proper dates.

Can someone guide me on this.

Labels (3)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

It is not clear what you consider to be a proper time format.

_time is automatically formatted so you could rename it and specify the format you want

index=abc ns=uio app_nameapi "ARC EVENT RECEIVED FROM SOURCE"| rex "RID:(?<RID>(\w+-){4}\w+)-(?<sourceagent>\w+-\w+)"|timechart count(RID) as "RID" by sourceagent
| rename _time as time
| fieldformat time=strftime(time,"%Y/%m/%d")

 

View solution in original post

ITWhisperer
SplunkTrust
SplunkTrust

It is not clear what you consider to be a proper time format.

_time is automatically formatted so you could rename it and specify the format you want

index=abc ns=uio app_nameapi "ARC EVENT RECEIVED FROM SOURCE"| rex "RID:(?<RID>(\w+-){4}\w+)-(?<sourceagent>\w+-\w+)"|timechart count(RID) as "RID" by sourceagent
| rename _time as time
| fieldformat time=strftime(time,"%Y/%m/%d")

 

Get Updates on the Splunk Community!

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

 Prepare to elevate your security operations with the powerful upgrade to Splunk Enterprise Security 8.x! This ...

Get Early Access to AI Playbook Authoring: Apply for the Alpha Private Preview ...

Passionate about security automation? Apply now to our AI Playbook Authoring Alpha private preview ...

Reduce and Transform Your Firewall Data with Splunk Data Management

Managing high-volume firewall data has always been a challenge. Noisy events and verbose traffic logs often ...