Skip to content

Commit d10bece

Browse files
authored
Merge pull request #13599 from mburke5678/logging-remove-docker
Removing references to Docker from Logging topics
2 parents a618303 + 83ddc19 commit d10bece

File tree

3 files changed

+1
-24
lines changed

3 files changed

+1
-24
lines changed

logging/efk-logging-exported-fields.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,6 @@ The fields are grouped in the following categories:
2020
* `exported-fields-rsyslog`
2121
* `exported-fields-systemd`
2222
* `exported-fields-kubernetes`
23-
* `exported-fields-docker`
2423
* `exported-fields-pipeline_metadata`
2524
* `exported-fields-ovirt`
2625
* `exported-fields-aushape`

modules/efk-logging-deploy-label.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
= Labeling nodes
77

88
At 100 nodes or more, it is recommended to first pre-pull the logging images
9-
from `docker pull registry.redhat.io/openshift3/logging-fluentd:v{product-version}`.
9+
from the registry.
1010
After deploying the logging infrastructure pods (Elasticsearch, Kibana, and
1111
Curator), node labeling should be done in steps of 20 nodes at a time. For
1212
example:

modules/efk-logging-exported-fields-docker.adoc

Lines changed: 0 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -2,28 +2,6 @@
22
//
33
// * logging/efk-logging-exported-fields.adoc
44

5-
[id='efk-logging-exported-fields-docker_{context}']
6-
= Docker exported fields
7-
8-
These are the Docker fields exported by the {product-title} cluster logging available for searching
9-
from Elasticsearch and Kibana.
10-
11-
Namespace for docker container-specific metadata. The `docker.container_id` is
12-
the Docker container ID.
13-
14-
[discrete]
15-
[[exported-fields-pipeline_metadata]]
16-
=== `pipeline_metadata` Fields
17-
18-
This includes metadata related to ViaQ log collection pipeline. Everything
19-
related to log collector, normalizers, and mappings goes here. Data in this
20-
subgroup is stored for troubleshooting and other purposes. The
21-
`pipeline_metadata.@version` field is the version of `com.redhat.viaq` mapping
22-
the document is intended to adhere by the normalizer. It must be set by the
23-
normalizer. The value must correspond to the [_meta][version]. For example,
24-
`class` with the description `TODO`, and `region` with the description region
25-
mapping.
26-
275
[discrete]
286
[[exported-fields-pipeline_metadata.collector]]
297
=== `pipeline_metadata.collector` Fields

0 commit comments

Comments
 (0)