All Apps and Add-ons

Dynamic Pulldown not populating with fields coming from automatic lookups

wpreston
Motivator

The Sideview Report Builder (and subsequent dynamic dropdowns that I've tried to create) will pick up the fields I've defined in props.conf/transforms.conf, but does not pick up any fields that are defined by an automatic lookup. For instance, I have a "User-ID" field that I extract from the logs, and I have an automatic lookup based on User-ID that creates the "Full-Name" field. So when the dropdown box populates, I get the User-ID field in the dynamic dropdown box, but not the Full-Name field.

I've run the search macro that is used in the Sideview Report Builder to get the data for the Fields dynamic dropdown box (get_fields_for_report_pulldowns). If I append that to the end of a normal search, it does show the fields that come from an automatic lookup, they just don't show up in a dynamic dropdown. How can I get the fields from automatic lookups to be present in the dynamic dropdown box?

1 Solution

sideview
SplunkTrust
SplunkTrust

Well Pulldown modules are regularly used to display both kinds of fields in various apps so I know that there is no fundamental problem here or fundamental difference between the treatment of each kind of field.

However I think what's happening is that your props.conf/transforms.conf extractions are scoped at the system level so that they run for all searches across all apps, whereas your automatic lookup configuration is instead scoped at the app level.

I will bet that you're testing out the search language in the app where the automatic lookups are defined, and the macro is finding the fields just fine, and then you're testing the Sideview Report Builder in the Sideview utils app (of course), and the automatic lookup config just does not run in that app context.

Can you check whether this is the case?

View solution in original post

0 Karma

sideview
SplunkTrust
SplunkTrust

Well Pulldown modules are regularly used to display both kinds of fields in various apps so I know that there is no fundamental problem here or fundamental difference between the treatment of each kind of field.

However I think what's happening is that your props.conf/transforms.conf extractions are scoped at the system level so that they run for all searches across all apps, whereas your automatic lookup configuration is instead scoped at the app level.

I will bet that you're testing out the search language in the app where the automatic lookups are defined, and the macro is finding the fields just fine, and then you're testing the Sideview Report Builder in the Sideview utils app (of course), and the automatic lookup config just does not run in that app context.

Can you check whether this is the case?

0 Karma

sideview
SplunkTrust
SplunkTrust

Great to hear. 😃

0 Karma

wpreston
Motivator

This was exactly the problem. Thank you for your answer!

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...