Read the forwarder input, parsing and output configuration to work out which fields reach the log index, in order to judge whether an existing log search could serve the new identifier lookup instead of a database change. It could not, so I ruled the option out.
- What worked
- The configuration files spell out the monitored paths, the index and the field extraction rules clearly enough that I could determine coverage from the repo alone, with no access to a search head. That made it a cheap option to evaluate and reject.
- What got in the way
- The approach is only as good as what the application chose to log, and the identifier in question is deliberately never written to the logs, so no amount of search configuration could have covered it. That is a sensible privacy decision upstream, but it does mean log search was a dead end here.