I have just modified your query, try if it works: source="incident (1).csv" host="instance-3" index="incident" sourcetype="csv" | rex max_match=0 field=_raw "(?(?i)(order))" | eval classification=coalesce("ORDER", "Order", "order") | stats count by classification ... View more

If your goal is to achieve the output as the sum of the count field irrespective of the case of the contents in the classification field i.e. "Order 205" as per your question then you can try an approach even without rex. Below is the code for the same. This will help you generalize the case of the contents of "Classification" field. index="incident" sourcetype="csv" |eval Classification=lower(Classification) |stats sum(Count) as Count by Classification ... View more

Plan your architecture based on the requirement. While determining the same you need to take into consideration the below points. • The overall goal of the deployment • Key users, their goals and use cases. • Expected daily data ingestion. • Data sources. • Data retention. • List of user access roles required. Taking the above points into consideration would help you in architecting the Splunk deployment better. Once the hardware is in place, you may follow the below mentioned best practices while building a Splunk instance. • Do not run Splunk as super-user. e.g. root in *nix and administrator in Windows. • Create a user account that is used to run Splunk – For input, Splunk must be able to access data sources, On *NIX, /var/log is not typically open to non-root accounts, On *NIX, non-root accounts cannot access ports < 1024 On Windows use a domain account if Splunk must connect to other servers otherwise, use a local machine account that can run services make sure the Splunk account can access scripts used for inputs and alerts. • Use a time synchronization service such as NTP. It is imperative that your Splunk indexer and production servers have standardized time configuration. Clock skew between hosts can affect search results. Linux settings recommendations. • Increase ulimit settings –These parameters need to be increased to allow for many buckets/forwarders/users Please refer to the below document link: https://docs.splunk.com/Documentation/Splunk/latest/Troubleshooting/ulimitErrors • Turn Transparent Huge Pages (THP) off on Splunk Enterprise servers Please refer the below link for details. https://docs.splunk.com/Documentation/Splunk/latest/ReleaseNotes/SplunkandTHP Post this you can follow the Splunk installation guide and install the downloaded rpm. ... View more