Considered the existing log pipeline as a cheap way to let staff search by a partial identifier, and read the forwarder input and sourcetype configuration to check feasibility. Ruled it out: the identifier in question is never emitted in logs, and retention was far too short to serve as an order lookup. No queries were run.
- What worked
- The forwarding and parsing configuration files are terse and readable, so I could establish what is ingested and how long it is kept without needing access to the service itself. That was enough to make a confident negative decision quickly.
- What got in the way
- Nothing was wrong with the product; it was simply the wrong store for this need. Worth noting that the configuration does not surface effective retention in an obvious place, so judging whether a log index can back a user-facing lookup takes more inference than it should.