Fix typos in runtime logs, field metadata, and reference docs

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 @@
 
 
 **`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
 
@@ -1569,23 +1569,23 @@
 
 
 **`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 @@
 
 
 **`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/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("log.file.path is not a string: %T", value)
+		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 {

filebeat/processor/add_kubernetes_metadata/matchers_test.go

@@ -126,6 +126,26 @@
 	executeTestWithResourceType(t, cfgLogsPath, cfgResourceType, source, expectedResult)
 }
 
+func TestLogsPathMatcher_NonStringLogPath(t *testing.T) {
+	testConfig := conf.NewConfig()
+
+	logger, observedLogs := logptest.NewTestingLoggerWithObserver(t, "")
+	logMatcher, err := newLogsPathMatcher(*testConfig, logger)
+	assert.NoError(t, err)
+
+	input := mapstr.M{
+		"log": mapstr.M{
+			"file": mapstr.M{
+				"path": 42,
+			},
+		},
+	}
+	output := logMatcher.MetadataIndex(input)
+
+	assert.Equal(t, "", output)
+	assert.Len(t, observedLogs.FilterMessageSnippet("log.file.path is not a string: int").TakeAll(), 1)
+}
+
 func TestLogsPathMatcher_InvalidVarLogPodSource(t *testing.T) {
 	cfgLogsPath := "/var/log/pods/"
 	cfgResourceType := "pod"
@@ -164,6 +184,32 @@
 	executeTestWithResourceType(t, cfgLogsPath, cfgResourceType, source, expectedResult)
 }
 
+func TestLogsPathMatcher_InvalidVarLogPodIDFormat_LogsPodUIDError(t *testing.T) {
+	cfgLogsPath := "/var/log/pods/"
+	cfgResourceType := "pod"
+	source := fmt.Sprintf("/var/log/pods/%s/container/0.log", puid)
+
+	testConfig := conf.NewConfig()
+	testConfig.SetString("logs_path", -1, cfgLogsPath)
+	testConfig.SetString("resource_type", -1, cfgResourceType)
+
+	logger, observedLogs := logptest.NewTestingLoggerWithObserver(t, "")
+	logMatcher, err := newLogsPathMatcher(*testConfig, logger)
+	assert.NoError(t, err)
+
+	input := mapstr.M{
+		"log": mapstr.M{
+			"file": mapstr.M{
+				"path": source,
+			},
+		},
+	}
+	output := logMatcher.MetadataIndex(input)
+
+	assert.Equal(t, "", output)
+	assert.Len(t, observedLogs.FilterMessageSnippet("Error extracting pod UID - source value does not contain matcher's logs_path").TakeAll(), 1)
+}
+
 func TestLogsPathMatcher_ValidVarLogPod(t *testing.T) {
 	cfgLogsPath := "/var/log/pods/"
 	cfgResourceType := "pod"
@@ -185,7 +231,7 @@
 func executeTestWithResourceType(t *testing.T, cfgLogsPath string, cfgResourceType string, source string, expectedResult string) {
 	testConfig := conf.NewConfig()
 	if cfgLogsPath != "" {
 		testConfig.SetString("logs_path", -1, cfgLogsPath)
 	}
 
 	if cfgResourceType != "" {

metricbeat/module/system/core/_meta/fields.yml

@@ -111,25 +111,25 @@
     - name: model_number
       type: keyword
       description: >
-        CPU model number. Only availabe on Linux
+        CPU model number. Only available on Linux
 
     - name: model_name
       type: keyword
       description: >
-        CPU model name. Only availabe on Linux
+        CPU model name. Only available on Linux
 
     - name: mhz
       type: float
       description: >
-        CPU core current clock. Only availabe on Linux
+        CPU core current clock. Only available on Linux
 
     - name: core_id
       type: keyword
       description: >
-        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
 
     - name: physical_id
       type: keyword
       description: >
-        CPU core physical ID. Only availabe on Linux
+        CPU core physical ID. Only available on Linux