Dashboards & Visualizations

drilldown click value issue

ypfbkg
Explorer

I have a hiddensearch:sourcetype="etrexacclog" instance="$instance$"

$instance$ is my click value

this click value is "server1:8080",but in my data , field instance data is "server:8080" or "server.ad.com:8080"

How could I set the click value to server1*:8080 (server1:8080 ==> server1*:8080)

Thanks.

Tags (2)
0 Karma
1 Solution

eelisio2
Path Finder

The replace() function should help:

sourcetype="etrexacclog"
| eval myfield="$instance$"
| eval myfield=replace(myfield,":",".ad.com:")
| where like(instance,"$instance$") OR like(instance,myfield)

View solution in original post

0 Karma

eelisio2
Path Finder

The replace() function should help:

sourcetype="etrexacclog"
| eval myfield="$instance$"
| eval myfield=replace(myfield,":",".ad.com:")
| where like(instance,"$instance$") OR like(instance,myfield)

0 Karma

eelisio2
Path Finder

Glad to help. Good luck.

0 Karma

ypfbkg
Explorer

Hi eelisio2,

Thanks for your help. it works now.
and i learned the where function

0 Karma

ypfbkg
Explorer

Hello jdunlea_splunk,
yes, click.value is different from the actual value of the field in the raw data.

raw data have two "server1:8080" & "server1.ad.com:8080"
click.value only "server1:8080"
i need click.value be "server1*:8080" to search "server1:8080" & "server1.ad.com:8080"

0 Karma

RicoSuave
Builder

can you please post all of your advanced xml?

0 Karma

jdunlea_splunk
Splunk Employee
Splunk Employee

Im not sure I understand? - If in your data, the value of "instance" is X, then the value of the click value should be X?

Are you saying that the click.value is different from the actual value of the field in the raw data??

0 Karma
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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

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 ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...