We are seeing a large discrepancy in field extraction counts between our Prod and Dev environments for sourcetype=xxx. In Prod, a search returns ~600+ fields. In Dev, the same search returns ~100 fields. We confirmed that KV_MODE=auto is set on both environments, but Dev still does not extract as many fields. Raw events in Dev do contain certain keys (e.g., PreStore), but these fields do not consistently appear in the sidebar unless explicitly searched. Prod has ~58 field extractions defined for this sourcetype, while Dev only has ~6. A large number of the extractions in Prod appear as Private in the UI. We are unclear whether these “Private” extractions are also being applied to other users, or only to the owners. Questions How do “Private” field extractions behave — are they ever applied to users other than the owner, or should they only affect the owner’s searches? Could differences in data verbosity (more key=value pairs in Prod logs) be compounding the discrepancy, even with the same KV_MODE setting? What is the best way to identify all active field extractions (including private/app-scoped) that are being applied to a sourcetype, so we can reconcile between environments? How can we ensure consistent field discovery behavior between Dev and Prod? Steps taken so far Checked props.conf and transforms.conf on the search app in both environments — only a few extractions found in Dev vs many in Prod. Verified KV_MODE settings using REST and btool. Confirmed Prod SH shows auto, Dev was updated to auto, but discrepancy remains. Compared number of field extractions and in PROD it is 58 for sourcetype and in Dev it is 6.
... View more