Dashboards & Visualizations

combining date fields into a single field for charting.

rhuss
Engager

Is it possible to somehow combine the date_year, date_month and date_mday fields into a single date field?

I need to do this for charting purposes.

Tags (1)
0 Karma
1 Solution

ziegfried
Influencer

Yes:

... | strcat date_year "-" date_month "-" date_mday date_str

or

... | eval datestr=date_year."-".date_month."-".date_mday

or

... | eval datestr=strftime(_time, "%Y-%m-%d")

I would suggest to use the last one, as it is possible that the date_* fields are missing from the event.

View solution in original post

justinhart
Path Finder

Try:

| eval full_date = date_year." ".date_month." ".date_mday

You can format that in whatever way you want, the area between " " is the seperator.

This was found under the eval command reference here.

ziegfried
Influencer

Yes:

... | strcat date_year "-" date_month "-" date_mday date_str

or

... | eval datestr=date_year."-".date_month."-".date_mday

or

... | eval datestr=strftime(_time, "%Y-%m-%d")

I would suggest to use the last one, as it is possible that the date_* fields are missing from the event.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...