libbeat/filebeat/metricbeat: fix typos in runtime errors, configs, and field descriptions

README.md

@@ -24,7 +24,7 @@ Beat  | Description
 [Metricbeat](https://github.com/elastic/beats/tree/main/metricbeat) | Fetches sets of metrics from the operating system and services
 [Packetbeat](https://github.com/elastic/beats/tree/main/packetbeat) | Monitors the network and applications by sniffing packets
 [Winlogbeat](https://github.com/elastic/beats/tree/main/winlogbeat) | Fetches and ships Windows Event logs
-[Osquerybeat](https://github.com/elastic/beats/tree/main/x-pack/osquerybeat) | Runs Osquery and manages interraction with it.
+[Osquerybeat](https://github.com/elastic/beats/tree/main/x-pack/osquerybeat) | Runs Osquery and manages interaction with it.
 
 In addition to the above Beats, which are officially supported by
 [Elastic](https://elastic.co), the community has created a set of other Beats

auditbeat/auditbeat.reference.yml

@@ -1000,7 +1000,7 @@ output.elasticsearch:
   # Path to the Kerberos configuration.
   #kerberos.config_path: /etc/krb5.conf
 
-  # The service name. Service principal name is contructed from
+  # The service name. Service principal name is constructed from
   # service_name/hostname@realm.
   #kerberos.service_name: kafka
 

docs/reference/auditbeat/add-nomad-metadata.md

@@ -85,7 +85,7 @@ Indexers and matchers are used to correlate fields in events with actual metadat
 
 Indexers use allocation metadata to create unique identifiers for each one of the pods.
 
-Avaliable indexers are:
+Available indexers are:
 
 `allocation_name`
 :   Identifies allocations by its name and namespace (as `<namespace>/<name>`)

docs/reference/auditbeat/configuration-ssl.md

@@ -266,7 +266,7 @@ Controls the verification of server certificates. Valid values are:
 
 ### `ca_trusted_fingerprint` [ca_trusted_fingerprint]
 
-A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normaly.
+A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normally.
 
 To get the fingerprint from a CA certificate on a Unix-like system, you can use the following command, where `ca.crt` is the certificate.
 

docs/reference/filebeat/add-nomad-metadata.md

@@ -85,7 +85,7 @@ Indexers and matchers are used to correlate fields in events with actual metadat
 
 Indexers use allocation metadata to create unique identifiers for each one of the pods.
 
-Avaliable indexers are:
+Available indexers are:
 
 `allocation_name`
 :   Identifies allocations by its name and namespace (as `<namespace>/<name>`)

docs/reference/filebeat/configuration-ssl.md

@@ -266,7 +266,7 @@ Controls the verification of server certificates. Valid values are:
 
 ### `ca_trusted_fingerprint` [ca_trusted_fingerprint]
 
-A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normaly.
+A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normally.
 
 To get the fingerprint from a CA certificate on a Unix-like system, you can use the following command, where `ca.crt` is the certificate.
 

docs/reference/filebeat/filebeat-input-container.md

@@ -120,7 +120,7 @@ Valid encodings:
 * `ebcdic-1040`: IBM CodePage 1140
 * `ebcdic-1047`: IBM CodePage 1047
 * `koi8r`: KOI8-R, Russian (Cyrillic)
-* `koi8u`: KOI8-U, Ukranian (Cyrillic)
+* `koi8u`: KOI8-U, Ukrainian (Cyrillic)
 * `macintosh`: Macintosh encoding
 * `macintosh-cyrillic`: Macintosh Cyrillic encoding
 * `windows1250`: Windows1250, Central and Eastern European

docs/reference/filebeat/filebeat-input-filestream.md

@@ -950,7 +950,7 @@ Valid encodings:
 * `ebcdic-1040`: IBM CodePage 1140
 * `ebcdic-1047`: IBM CodePage 1047
 * `koi8r`: KOI8-R, Russian (Cyrillic)
-* `koi8u`: KOI8-U, Ukranian (Cyrillic)
+* `koi8u`: KOI8-U, Ukrainian (Cyrillic)
 * `macintosh`: Macintosh encoding
 * `macintosh-cyrillic`: Macintosh Cyrillic encoding
 * `windows1250`: Windows1250, Central and Eastern European

docs/reference/filebeat/filebeat-input-log.md

@@ -158,7 +158,7 @@ Valid encodings:
 * `ebcdic-1040`: IBM CodePage 1140
 * `ebcdic-1047`: IBM CodePage 1047
 * `koi8r`: KOI8-R, Russian (Cyrillic)
-* `koi8u`: KOI8-U, Ukranian (Cyrillic)
+* `koi8u`: KOI8-U, Ukrainian (Cyrillic)
 * `macintosh`: Macintosh encoding
 * `macintosh-cyrillic`: Macintosh Cyrillic encoding
 * `windows1250`: Windows1250, Central and Eastern European

docs/reference/filebeat/filebeat-input-stdin.md

@@ -67,7 +67,7 @@ Valid encodings:
 * `ebcdic-1040`: IBM CodePage 1140
 * `ebcdic-1047`: IBM CodePage 1047
 * `koi8r`: KOI8-R, Russian (Cyrillic)
-* `koi8u`: KOI8-U, Ukranian (Cyrillic)
+* `koi8u`: KOI8-U, Ukrainian (Cyrillic)
 * `macintosh`: Macintosh encoding
 * `macintosh-cyrillic`: Macintosh Cyrillic encoding
 * `windows1250`: Windows1250, Central and Eastern European

docs/reference/heartbeat/add-nomad-metadata.md

@@ -85,7 +85,7 @@ Indexers and matchers are used to correlate fields in events with actual metadat
 
 Indexers use allocation metadata to create unique identifiers for each one of the pods.
 
-Avaliable indexers are:
+Available indexers are:
 
 `allocation_name`
 :   Identifies allocations by its name and namespace (as `<namespace>/<name>`)

docs/reference/heartbeat/configuration-ssl.md

@@ -279,7 +279,7 @@ Controls the verification of server certificates. Valid values are:
 
 ### `ca_trusted_fingerprint` [ca_trusted_fingerprint]
 
-A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normaly.
+A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normally.
 
 To get the fingerprint from a CA certificate on a Unix-like system, you can use the following command, where `ca.crt` is the certificate.
 

docs/reference/metricbeat/add-nomad-metadata.md

@@ -85,7 +85,7 @@ Indexers and matchers are used to correlate fields in events with actual metadat
 
 Indexers use allocation metadata to create unique identifiers for each one of the pods.
 
-Avaliable indexers are:
+Available indexers are:
 
 `allocation_name`
 :   Identifies allocations by its name and namespace (as `<namespace>/<name>`)

docs/reference/metricbeat/configuration-ssl.md

@@ -281,7 +281,7 @@ Controls the verification of server certificates. Valid values are:
 
 ### `ca_trusted_fingerprint` [ca_trusted_fingerprint]
 
-A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normaly.
+A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normally.
 
 To get the fingerprint from a CA certificate on a Unix-like system, you can use the following command, where `ca.crt` is the certificate.
 

docs/reference/metricbeat/exported-fields-system.md

@@ -179,31 +179,31 @@ Process metrics.
 
 
 **`system.core.model_number`**
-:   CPU model number. Only availabe on Linux
+:   CPU model number. Only available on Linux
 
     type: keyword
 
 
 **`system.core.model_name`**
-:   CPU model name. Only availabe on Linux
+:   CPU model name. Only available on Linux
 
     type: keyword
 
 
 **`system.core.mhz`**
-:   CPU core current clock. Only availabe on Linux
+:   CPU core current clock. Only available on Linux
 
     type: float
 
 
 **`system.core.core_id`**
-:   CPU physical core ID. One core might might execute multiple threads, hence more than one `system.core.id` can share the same `system.core.core_id`. Only availabe on Linux
+:   CPU physical core ID. One core might execute multiple threads, hence more than one `system.core.id` can share the same `system.core.core_id`. Only available on Linux
 
     type: keyword
 
 
 **`system.core.physical_id`**
-:   CPU core physical ID. Only availabe on Linux
+:   CPU core physical ID. Only available on Linux
 
     type: keyword
 
@@ -469,7 +469,7 @@ Process metrics.
 
 
 **`system.diskio.io.time`**
-:   The total number of of milliseconds spent doing I/Os.
+:   The total number of milliseconds spent doing I/Os.
 
     type: long
 
@@ -1569,23 +1569,23 @@ Memory limits and metrics.
 
 
 **`system.process.cgroup.memory.mem.low.bytes`**
-:   memory low threshhold
+:   memory low threshold
 
     type: long
 
     format: bytes
 
 
 **`system.process.cgroup.memory.mem.high.bytes`**
-:   memory high threshhold
+:   memory high threshold
 
     type: long
 
     format: bytes
 
 
 **`system.process.cgroup.memory.mem.max.bytes`**
-:   memory max threshhold
+:   memory max threshold
 
     type: long
 
@@ -1657,23 +1657,23 @@ number of times the controller tripped a given usage level
 
 
 **`system.process.cgroup.memory.memsw.low.bytes`**
-:   memory low threshhold
+:   memory low threshold
 
     type: long
 
     format: bytes
 
 
 **`system.process.cgroup.memory.memsw.high.bytes`**
-:   memory high threshhold
+:   memory high threshold
 
     type: long
 
     format: bytes
 
 
 **`system.process.cgroup.memory.memsw.max.bytes`**
-:   memory max threshhold
+:   memory max threshold
 
     type: long
 

docs/reference/packetbeat/add-nomad-metadata.md

@@ -85,7 +85,7 @@ Indexers and matchers are used to correlate fields in events with actual metadat
 
 Indexers use allocation metadata to create unique identifiers for each one of the pods.
 
-Avaliable indexers are:
+Available indexers are:
 
 `allocation_name`
 :   Identifies allocations by its name and namespace (as `<namespace>/<name>`)

docs/reference/packetbeat/configuration-ssl.md

@@ -266,7 +266,7 @@ Controls the verification of server certificates. Valid values are:
 
 ### `ca_trusted_fingerprint` [ca_trusted_fingerprint]
 
-A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normaly.
+A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normally.
 
 To get the fingerprint from a CA certificate on a Unix-like system, you can use the following command, where `ca.crt` is the certificate.
 

docs/reference/winlogbeat/add-nomad-metadata.md

@@ -85,7 +85,7 @@ Indexers and matchers are used to correlate fields in events with actual metadat
 
 Indexers use allocation metadata to create unique identifiers for each one of the pods.
 
-Avaliable indexers are:
+Available indexers are:
 
 `allocation_name`
 :   Identifies allocations by its name and namespace (as `<namespace>/<name>`)

docs/reference/winlogbeat/configuration-ssl.md

@@ -266,7 +266,7 @@ Controls the verification of server certificates. Valid values are:
 
 ### `ca_trusted_fingerprint` [ca_trusted_fingerprint]
 
-A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normaly.
+A HEX encoded SHA-256 of a CA certificate. If this certificate is present in the chain during the handshake, it will be added to the `certificate_authorities` list and the handshake will continue normally.
 
 To get the fingerprint from a CA certificate on a Unix-like system, you can use the following command, where `ca.crt` is the certificate.
 

filebeat/_meta/config/filebeat.inputs.reference.yml.tmpl

@@ -251,7 +251,7 @@ filebeat.inputs:
   # To fetch all ".log" files from a specific level of subdirectories
   # /var/log/*/*.log can be used.
   # For each file found under this path, a harvester is started.
-  # Make sure not file is defined twice as this can lead to unexpected behaviour.
+  # Make sure no file is defined twice as this can lead to unexpected behaviour.
   paths:
     - /var/log/*.log
     #- c:\programdata\elasticsearch\logs\*
@@ -346,7 +346,7 @@ filebeat.inputs:
 
   #### Filtering messages
 
-  # You can filter messsages in the parsers pipeline. Use this method if you would like to
+  # You can filter messages in the parsers pipeline. Use this method if you would like to
   # include or exclude lines before they are aggregated into multiline or the JSON contents
   # are parsed.
 

filebeat/filebeat.reference.yml

@@ -664,7 +664,7 @@ filebeat.inputs:
   # To fetch all ".log" files from a specific level of subdirectories
   # /var/log/*/*.log can be used.
   # For each file found under this path, a harvester is started.
-  # Make sure not file is defined twice as this can lead to unexpected behaviour.
+  # Make sure no file is defined twice as this can lead to unexpected behaviour.
   paths:
     - /var/log/*.log
     #- c:\programdata\elasticsearch\logs\*
@@ -759,7 +759,7 @@ filebeat.inputs:
 
   #### Filtering messages
 
-  # You can filter messsages in the parsers pipeline. Use this method if you would like to
+  # You can filter messages in the parsers pipeline. Use this method if you would like to
   # include or exclude lines before they are aggregated into multiline or the JSON contents
   # are parsed.
 
@@ -2264,7 +2264,7 @@ output.elasticsearch:
   # Path to the Kerberos configuration.
   #kerberos.config_path: /etc/krb5.conf
 
-  # The service name. Service principal name is contructed from
+  # The service name. Service principal name is constructed from
   # service_name/hostname@realm.
   #kerberos.service_name: kafka
 

filebeat/input/filestream/internal/input-logfile/store.go

@@ -870,7 +870,7 @@ func readStates(log *logp.Logger, store *statestore.Store, prefix string) (*stat
 
 		var st state
 		if err := dec.Decode(&st); err != nil {
-			log.Errorf("Failed to read regisry state for '%v', cursor state will be ignored. Error was: %+v",
+			log.Errorf("Failed to read registry state for '%v', cursor state will be ignored. Error was: %+v",
 				key, err)
 			return true, nil
 		}

filebeat/processor/add_kubernetes_metadata/matchers.go

@@ -88,7 +88,11 @@ func (f *LogPathMatcher) MetadataIndex(event mapstr.M) string {
 		return ""
 	}
 
-	source := value.(string)
+	source, ok := value.(string)
+	if !ok {
+		f.logger.Debugf("Error extracting log.file.path from the event: value is not a string.")
+		return ""
+	}
 	f.logger.Debugf("Incoming log.file.path value: %s", source)
 
 	if !strings.Contains(source, f.LogsPath) {
@@ -128,7 +132,7 @@ func (f *LogPathMatcher) MetadataIndex(event mapstr.M) string {
 				}
 			}
 
-			f.logger.Error("Error extracting pod uid - source value does not contains matcher's logs_path")
+			f.logger.Error("Error extracting pod UID - source value does not contain matcher's logs_path")
 			return ""
 		}
 	} else {

heartbeat/heartbeat.reference.yml

@@ -1083,7 +1083,7 @@ output.elasticsearch:
   # Path to the Kerberos configuration.
   #kerberos.config_path: /etc/krb5.conf
 
-  # The service name. Service principal name is contructed from
+  # The service name. Service principal name is constructed from
   # service_name/hostname@realm.
   #kerberos.service_name: kafka
 

libbeat/_meta/config/output-kafka.reference.yml.tmpl

@@ -149,7 +149,7 @@
   # Path to the Kerberos configuration.
   #kerberos.config_path: /etc/krb5.conf
 
-  # The service name. Service principal name is contructed from
+  # The service name. Service principal name is constructed from
   # service_name/hostname@realm.
   #kerberos.service_name: kafka
 

libbeat/autodiscover/README.md

@@ -178,10 +178,10 @@ spec:
 Everything works the same as Autodiscover without LeaderElection until step 8.
 
 8. If there is no conditions in the template set by the user, the configs will be generated from [hints](https://github.com/elastic/beats/blob/4b1f69923b3f2abbbf1860295fe5dbff7db3d63c/libbeat/autodiscover/providers/kubernetes/kubernetes.go#L186).
-9. Wether hints are enabled or not is part of the [Kubernetes Provider struct](https://github.com/elastic/beats/blob/4b1f69923b3f2abbbf1860295fe5dbff7db3d63c/libbeat/autodiscover/providers/kubernetes/kubernetes.go#L121) builders field.
+9. Whether hints are enabled or not is part of the [Kubernetes Provider struct](https://github.com/elastic/beats/blob/4b1f69923b3f2abbbf1860295fe5dbff7db3d63c/libbeat/autodiscover/providers/kubernetes/kubernetes.go#L121) builders field.
 10. [GenerateHints](https://github.com/elastic/beats/blob/eff92354db783001880f4bade9f59942fca747ba/libbeat/autodiscover/builder/helper.go#L213) function looks into the event's annotations. A [hints map](https://github.com/elastic/beats/blob/eff92354db783001880f4bade9f59942fca747ba/libbeat/autodiscover/builder/helper.go#L226) is created with all hints and returned.
 11. From those hints, configs are [created](https://github.com/elastic/beats/blob/4b1f69923b3f2abbbf1860295fe5dbff7db3d63c/libbeat/autodiscover/builder.go#L97) in the same form as in `Autodiscover without LeaderElection` step 8.
-    They contain the same information as if they where set explicitly in the metricbeat configureation but actually derive from the pod annotations.
+    They contain the same information as if they were set explicitly in the Metricbeat configuration but actually derive from the pod annotations.
 12. Those configs are then [added](https://github.com/elastic/beats/blob/4b1f69923b3f2abbbf1860295fe5dbff7db3d63c/libbeat/autodiscover/providers/kubernetes/kubernetes.go#L197) in the event and gets published.
 13. The process after that is same as in `Autodiscover without LeaderElection` step 9 and onward.
 

libbeat/cmd/completion.go

@@ -29,22 +29,22 @@ import (
 func genCompletionCmd(_ instance.Settings, rootCmd *BeatsRootCmd) *cobra.Command {
 	completionCmd := cobra.Command{
 		Use:   "completion SHELL",
-		Short: "Output shell completion code for the specified shell (bash and zsh only by the moment)",
+		Short: "Output shell completion code for the specified shell (bash and zsh only for now)",
 		// We don't want to expose this one in help:
 		Hidden: true,
 		Run: func(cmd *cobra.Command, args []string) {
 			if len(args) != 1 {
-				fmt.Println("Expected one argument with the desired shell")
+				fmt.Println("Expected one argument with the desired shell") //nolint:forbidigo // preserving existing stdout behavior
 				os.Exit(1)
 			}
 
 			switch args[0] {
 			case "bash":
-				rootCmd.GenBashCompletion(os.Stdout)
+				_ = rootCmd.GenBashCompletion(os.Stdout)
 			case "zsh":
-				rootCmd.GenZshCompletion(os.Stdout)
+				_ = rootCmd.GenZshCompletion(os.Stdout)
 			default:
-				fmt.Printf("Unknown shell %s, only bash and zsh are available\n", args[0])
+				fmt.Printf("Unknown shell %s, only bash and zsh are available\n", args[0]) //nolint:forbidigo // preserving existing stdout behavior
 				os.Exit(1)
 			}
 		},