Dashboards & Visualizations

Splunk Dashboard - <eval>

pcontreras
Explorer

Hello there!

I'm trying to use <change> and <eval> inside of my time input to create a token that takes in $time.earliest$ and converts it to a unix timestamp, however, my <eval> is not working how I expect.

pcontreras_0-1698362424842.png


When I use $start_time$ in my dashboard panels, I get a literal copy/paste of the "relative_time(now() ..." statement (i.e., it's not actually evaluating).  I've seen multiple examples in Splunk documentation and it seems like <eval> is supposed to evaluate the function you're trying to use.

Help me, Splunk Community.  You're my only hope.

Labels (3)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

There doesn't appear to be anything wrong with what you are doing (apart from I don't think you need the quotes around the token in the relative_time function, and the condition is probably superfluous); the issue may be to do with the version of Splunk you are using as there have been issues with this before iirc. Which version are you using?

0 Karma

pcontreras
Explorer

I'm on Splunk Cloud version 9.0.2305.201.

Don't I need the quotes in the relative_time function?  If $time.earliest$ is a relative time modifier (e.g., -7d@h), it needs quotes, right?

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

I am using enterprise and it works without quotes with -7d@h

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to January Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...

[Puzzles] Solve, Learn, Repeat: Reprocessing XML into Fixed-Length Events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...