Remove links and references to journalbeat (elastic#1893) (elastic#1894)

lockewritesdocs · Nov 24, 2021 · 1d3bfb5 · 1d3bfb5
1 parent 6614100
commit 1d3bfb5
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 12 deletions.
diff --git a/docs/en/getting-started/get-started-stack.asciidoc b/docs/en/getting-started/get-started-stack.asciidoc
@@ -438,7 +438,6 @@ Started documentation:
 |{filebeat-ref}/filebeat-installation-configuration.html[{filebeat}] |Log files
 |{functionbeat-ref}/functionbeat-installation-configuration.html[{functionbeat}] |Cloud data
 |{heartbeat-ref}/heartbeat-installation-configuration.html[{heartbeat}] |Availability monitoring
-|{journalbeat-ref}/journalbeat-installation-configuration.html[{journalbeat}] |Systemd journals
 |{metricbeat-ref}/metricbeat-installation-configuration.html[{metricbeat}] |Metrics
 |{packetbeat-ref}/packetbeat-installation-configuration.html[{packetbeat}] |Network traffic
 |{winlogbeat-ref}/winlogbeat-installation-configuration.html[{winlogbeat}] |Windows event logs

diff --git a/docs/en/gke-on-prem/gke-on-prem-deploy-beats.asciidoc b/docs/en/gke-on-prem/gke-on-prem-deploy-beats.asciidoc
@@ -79,22 +79,12 @@ kubectl create -f filebeat-kubernetes.yaml
 kubectl create -f metricbeat-kubernetes.yaml
 ----
 
-NOTE: Depending on your k8s node configuration, you may not need to deploy
-{journalbeat}. If your Nodes use journald for logging, then deploy {journalbeat}.
-Otherwise, {filebeat} will get the logs.
-
-[source,sh]
-----
-kubectl create -f journalbeat-kubernetes.yaml
-----
-
 [discrete]
 [[verify-beats]]
 === Verify
 
 Check for the running DaemonSets.
-Verify that there is one {filebeat}, {metricbeat}, and {journalbeat} pod per
-k8s Node running.
+Verify that there is one {filebeat} and {metricbeat} pod per k8s Node running.
 
 [source,sh]
 ----