Dashboards & Visualizations

How to insert a static column in a table with drilldown to a custom link?

vikas_gopal
Builder

Hi Experts ,

I have a very basic requirement . I want to display only one table and it should have one static column value lets say "Link" which I want to further drill down to my custom link.
I am so irritated that I am not even know that How I can add a static column .

Please suggest

0 Karma

vikas_gopal
Builder

I found the solution I used eval for example

index=_internal |table Incident, host | eval Incident="123" | dedup host

with this a new column incident has been added to the table with the static value 123.

sowings
Splunk Employee
Splunk Employee

You've already found that using eval can provide you with a static value for a field.

Next, you'll want to couple this with the simple XML drilldown specification in your dashboard. The new field that you've created (here, you've called it Incident) would then be provided to a drilldown value. The syntax for the drilldown of the table might look like this:

  <table>
    ...
    <drilldown>
      <link>/app/<yourapp>/<yourview>/?query\_param=$row.Incident$<link>
   </drilldown>
  </table>

The "row.Incident" is the value of the Incident field within the row that was clicked. If your target is a Splunk form, the "query_param" part might be "form.Incident", depending upon the name of the field in the target view (while always having "form." as a prefix to call it out as a field for the form).

0 Karma
Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

 Ready to master Kubernetes and cloud monitoring like the pros? Join Splunk’s Growth Engineering team for an ...

Update Your SOAR Apps for Python 3.13: What Community Developers Need to Know

To Community SOAR App Developers - we're reaching out with an important update regarding Python 3.9's ...

October Community Champions: A Shoutout to Our Contributors!

As October comes to a close, we want to take a moment to celebrate the people who make the Splunk Community ...