Splunk Search

Lookup table issues devices

adrianrepublic
Explorer

We have been using a lookup table for many customers who are separated via separate indexes.

The table is simple but drives our device dashboard data using a customer_id_tok for dropdowns. Each customer has a different prefix e.g 1100001 (customer A) and 1500002(customer B) on the lookup.

However we have devices that have written to two or three indexes over time as we have reused the devices for different customers when fixed.

This now seems to have caused a problem on individual customer dashboards as they can see the "customer_id" which is for another customer in the lookup as the device historically was linked to another "customer_id"

Is there anyway of segregating via the token or some other way so that the dashboard dropdown can only see say customer_id's prefixed with say 11 or their matching prefix?

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!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...