Dashboards & Visualizations

$click.value2$ can't work with fieldformat

to4kawa
Ultra Champion

 

 

 

<dashboard>
  <label>drilldown time</label>
  <init>
    <unset token="epoch" />
    <unset token="human" />
  </init>
  <row>
    <panel>
      <table>
        <search>
          <query>|makeresults |eval time=_time| fieldformat time=strftime(time,"%F %T")</query>
          <earliest>-24h@h</earliest>
          <latest>now</latest>
          <sampleRatio>1</sampleRatio>
        </search>
        <drilldown>
          <set token="epoch">$click.value2$</set>
          <eval token="human">strftime($epoch$,"%F%T")</eval>
        </drilldown>
      </table>
    </panel>
  </row>
  <row>
    <panel>
      <html>
        <p>
          <h2>$epoch$</h2>
        </p>
        <p>
          <h2>$human$</h2>
        </p>
      </html>
    </panel>
  </row>
</dashboard>

 

 

 

-   click _time, fine
-   click time, not work

What else can I do besides rename X as _time?


Labels (1)
0 Karma
1 Solution

bowesmana
SplunkTrust
SplunkTrust

Given that the fieldformat time is ISO, not epoch as expected, just reverse the strXtime logic

<dashboard>
  <label>drilldown time</label>
  <init>
    <unset token="epoch" />
    <unset token="human" />
  </init>
  <row>
    <panel>
      <table>
        <search>
          <query>|makeresults |eval time=_time| fieldformat time=strftime(time,"%F %T")</query>
          <earliest>-24h@h</earliest>
          <latest>now</latest>
          <sampleRatio>1</sampleRatio>
        </search>
        <drilldown>
          <set token="epoch">$click.value2$</set>
          <eval token="human">strftime($epoch$,"%F %T")</eval>
          <set token="human2">$row.time$</set>
          <eval token="epoch2">strptime($human2$,"%F %T")</eval>
        </drilldown>
      </table>
    </panel>
  </row>
  <row>
    <panel>
      <html>
        <p>
          <h2>EPOCH: $epoch$</h2>
        </p>
        <p>
          <h2>HUMAN: $human$</h2>
        </p>
        <p>
          <h2>EPOCH2: $epoch2$</h2>
        </p>
        <p>
          <h2>HUMAN2: $human2$</h2>
        </p>
      </html>
    </panel>
  </row>
</dashboard>

View solution in original post

bowesmana
SplunkTrust
SplunkTrust

Given that the fieldformat time is ISO, not epoch as expected, just reverse the strXtime logic

<dashboard>
  <label>drilldown time</label>
  <init>
    <unset token="epoch" />
    <unset token="human" />
  </init>
  <row>
    <panel>
      <table>
        <search>
          <query>|makeresults |eval time=_time| fieldformat time=strftime(time,"%F %T")</query>
          <earliest>-24h@h</earliest>
          <latest>now</latest>
          <sampleRatio>1</sampleRatio>
        </search>
        <drilldown>
          <set token="epoch">$click.value2$</set>
          <eval token="human">strftime($epoch$,"%F %T")</eval>
          <set token="human2">$row.time$</set>
          <eval token="epoch2">strptime($human2$,"%F %T")</eval>
        </drilldown>
      </table>
    </panel>
  </row>
  <row>
    <panel>
      <html>
        <p>
          <h2>EPOCH: $epoch$</h2>
        </p>
        <p>
          <h2>HUMAN: $human$</h2>
        </p>
        <p>
          <h2>EPOCH2: $epoch2$</h2>
        </p>
        <p>
          <h2>HUMAN2: $human2$</h2>
        </p>
      </html>
    </panel>
  </row>
</dashboard>

to4kawa
Ultra Champion

thanks @bowesmana 
I want epoch time value and it displays human readable , and to get the original epoch value by drilldown.

I'm trying to figure out how to do this when there are multiple time fields.

It's easy to get it with human readable and convert it to epoch with strptime.

0 Karma
Get Updates on the Splunk Community!

Celebrating Fast Lane: 2025 Authorized Learning Partner of the Year

At .conf25, Splunk proudly recognized Fast Lane as the 2025 Authorized Learning Partner of the Year. This ...

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...