Inspected the existing forwarder sidecar and inputs as a possible search backend, rejected it for production order and subscriber lookup, then only added a log input so the new indexer ships logs the same way as the other services.
- What worked
- The existing forwarder config was easy to extend for another service’s log file, and the log-shipping role was already obvious from the in-pod setup.
- What got in the way
- Splunk was the wrong product for CRM-style identifier search: it is aimed at operational logs, not isolated low-latency business-record lookup, and mixing those workloads would have put search on the observability path.