|  | @@ -1,12 +1,12 @@
 | 
	
		
			
				|  |  | -[[ingest-useragent]]
 | 
	
		
			
				|  |  | -=== Ingest Useragent Processor Plugin
 | 
	
		
			
				|  |  | +[[ingest-user-agent]]
 | 
	
		
			
				|  |  | +=== Ingest user agent processor plugin
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -The Useragent processor extracts details from the user agent string a browser sends with its web requests. 
 | 
	
		
			
				|  |  | -This processor adds this information by default under the `useragent` field.
 | 
	
		
			
				|  |  | +The `user_agent` processor extracts details from the user agent string a browser sends with its web requests.
 | 
	
		
			
				|  |  | +This processor adds this information by default under the `user_agent` field.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -The ingest-useragent plugin ships by default with the regexes.yaml made available by uap-java with an Apache 2.0 license. For more details see https://github.com/ua-parser/uap-core.
 | 
	
		
			
				|  |  | +The ingest-user-agent plugin ships by default with the regexes.yaml made available by uap-java with an Apache 2.0 license. For more details see https://github.com/ua-parser/uap-core.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -[[ingest-useragent-install]]
 | 
	
		
			
				|  |  | +[[ingest-user-agent-install]]
 | 
	
		
			
				|  |  |  [float]
 | 
	
		
			
				|  |  |  ==== Installation
 | 
	
		
			
				|  |  |  
 | 
	
	
		
			
				|  | @@ -14,13 +14,13 @@ This plugin can be installed using the plugin manager:
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  [source,sh]
 | 
	
		
			
				|  |  |  ----------------------------------------------------------------
 | 
	
		
			
				|  |  | -sudo bin/elasticsearch-plugin install ingest-useragent
 | 
	
		
			
				|  |  | +sudo bin/elasticsearch-plugin install ingest-user-agent
 | 
	
		
			
				|  |  |  ----------------------------------------------------------------
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  The plugin must be installed on every node in the cluster, and each node must
 | 
	
		
			
				|  |  |  be restarted after installation.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -[[ingest-useragent-remove]]
 | 
	
		
			
				|  |  | +[[ingest-user-agent-remove]]
 | 
	
		
			
				|  |  |  [float]
 | 
	
		
			
				|  |  |  ==== Removal
 | 
	
		
			
				|  |  |  
 | 
	
	
		
			
				|  | @@ -28,26 +28,26 @@ The plugin can be removed with the following command:
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  [source,sh]
 | 
	
		
			
				|  |  |  ----------------------------------------------------------------
 | 
	
		
			
				|  |  | -sudo bin/elasticsearch-plugin remove ingest-useragent
 | 
	
		
			
				|  |  | +sudo bin/elasticsearch-plugin remove ingest-user-agent
 | 
	
		
			
				|  |  |  ----------------------------------------------------------------
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  The node must be stopped before removing the plugin.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -[[using-ingest-useragent]]
 | 
	
		
			
				|  |  | -==== Using the Useragent Processor in a Pipeline
 | 
	
		
			
				|  |  | +[[using-ingest-user-agent]]
 | 
	
		
			
				|  |  | +==== Using the user_agent Processor in a Pipeline
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -[[ingest-useragent-options]]
 | 
	
		
			
				|  |  | -.Useragent options
 | 
	
		
			
				|  |  | +[[ingest-user-agent-options]]
 | 
	
		
			
				|  |  | +.User-agent options
 | 
	
		
			
				|  |  |  [options="header"]
 | 
	
		
			
				|  |  |  |======
 | 
	
		
			
				|  |  |  | Name                   | Required  | Default                                                                            | Description
 | 
	
		
			
				|  |  |  | `field`                | yes       | -                                                                                  | The field containing the user agent string.
 | 
	
		
			
				|  |  | -| `target_field`         | no        | useragent                                                                          | The field that will be filled with the user agent details.
 | 
	
		
			
				|  |  | -| `regex_file`           | no        | -                                                                                  | The name of the file in the `config/ingest-useragent` directory containing the regular expressions for parsing the user agent string. Both the directory and the file have to be created before starting Elasticsearch. If not specified, ingest-useragent will use the regexes.yaml from uap-core it ships with (see below).
 | 
	
		
			
				|  |  | +| `target_field`         | no        | user_agent                                                                          | The field that will be filled with the user agent details.
 | 
	
		
			
				|  |  | +| `regex_file`           | no        | -                                                                                  | The name of the file in the `config/ingest-user-agent` directory containing the regular expressions for parsing the user agent string. Both the directory and the file have to be created before starting Elasticsearch. If not specified, ingest-user-agent will use the regexes.yaml from uap-core it ships with (see below).
 | 
	
		
			
				|  |  |  | `properties`           | no        | [`name`, `major`, `minor`, `patch`, `build`, `os`, `os_name`, `os_major`, `os_minor`, `device`] | Controls what properties are added to `target_field`.
 | 
	
		
			
				|  |  |  |======
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -Here is an example that adds the user agent details to the `useragent` field based on the `agent` field:
 | 
	
		
			
				|  |  | +Here is an example that adds the user agent details to the `user_agent` field based on the `agent` field:
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  [source,js]
 | 
	
		
			
				|  |  |  --------------------------------------------------
 | 
	
	
		
			
				|  | @@ -55,7 +55,7 @@ Here is an example that adds the user agent details to the `useragent` field bas
 | 
	
		
			
				|  |  |    "description" : "...",
 | 
	
		
			
				|  |  |    "processors" : [
 | 
	
		
			
				|  |  |      {
 | 
	
		
			
				|  |  | -      "useragent" : {
 | 
	
		
			
				|  |  | +      "user_agent" : {
 | 
	
		
			
				|  |  |          "field" : "agent"
 | 
	
		
			
				|  |  |        }
 | 
	
		
			
				|  |  |      }
 | 
	
	
		
			
				|  | @@ -64,11 +64,11 @@ Here is an example that adds the user agent details to the `useragent` field bas
 | 
	
		
			
				|  |  |  --------------------------------------------------
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  ===== Using a custom regex file
 | 
	
		
			
				|  |  | -To use a custom regex file for parsing the user agents, that file has to be put into the `config/ingest-useragent` directory and
 | 
	
		
			
				|  |  | +To use a custom regex file for parsing the user agents, that file has to be put into the `config/ingest-user-agent` directory and
 | 
	
		
			
				|  |  |  has to have a `.yaml` filename extension. The file has to be present at node startup, any changes to it or any new files added
 | 
	
		
			
				|  |  |  while the node is running will not have any effect.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  In practice, it will make most sense for any custom regex file to be a variant of the default file, either a more recent version
 | 
	
		
			
				|  |  |  or a customised version.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -The default file included in `ingest-useragent` is the `regexes.yaml` from uap-core: https://github.com/ua-parser/uap-core/blob/master/regexes.yaml 
 | 
	
		
			
				|  |  | +The default file included in `ingest-user-agent` is the `regexes.yaml` from uap-core: https://github.com/ua-parser/uap-core/blob/master/regexes.yaml
 |