From db70253cfe7a55181a1572b8d01f0945acfff1c1 Mon Sep 17 00:00:00 2001 From: DeDe Morton Date: Fri, 30 Jul 2021 13:32:35 -0700 Subject: [PATCH] Remove review comments and add missing support statement (#932) --- .../beats-agent-comparison.asciidoc | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/docs/en/ingest-management/beats-agent-comparison.asciidoc b/docs/en/ingest-management/beats-agent-comparison.asciidoc index b110f7ae04..6aa9272286 100644 --- a/docs/en/ingest-management/beats-agent-comparison.asciidoc +++ b/docs/en/ingest-management/beats-agent-comparison.asciidoc @@ -1,10 +1,6 @@ [[beats-agent-comparison]] = {beats} and {agent} capabilities -//QUESTION: I think we need a short intro here for new users who don't know -//about Beats, but might need to consider using it if the service they want to -//monitor is not yet covered by agent. Is this good enough? - Elastic provides two main ways to send data to {es}: * *{beats}* are lightweight data shippers that send operational data to @@ -12,12 +8,6 @@ Elastic provides two main ways to send data to {es}: logs, metrics, and uptime. Depending on what data you want to collect, you may need to install mutliple shippers on a single host. -//QUESTION: Should I list the Beats by name here? Or maybe describe capabilities: -//audit data, log files, cloud data, availability, systems journals, metrics, -//network traffic, and Windows event logs." when written out, it's clear that -//beats have more functionality right now. That's true, but is that what we -//want to convey? - * *{agent}* is a single agent for logs, metrics, security data, and threat prevention. {agent} supports central management through {fleet}. @@ -125,7 +115,7 @@ The following table shows the inputs supported by the {agent} in {version}: |UNIX |{y} (beta) -|NEED INFO HERE +|{y} (beta) |=== [discrete] @@ -137,8 +127,6 @@ The following table shows the outputs supported by the {agent} in {version}: NOTE: {endpoint-sec} has a different output matrix. -//QUESTION: Is the endpoint matrix available somewhere so that I can point to it? - [options,header] |=== |Output |Beats |{fleet}-managed {agent} |Standalone {agent} @@ -183,11 +171,6 @@ NOTE: {endpoint-sec} has a different output matrix. [[supported-configurations]] == Supported configurations -//QUESTION: I've removed the verbs and gerunds from the config description -//because they made the info harder to scan. I think the verb/gerund is -//implied by the section title here and not required. Plus the link to the Beats -//docs removes ambiguities. - [options,header] |=== |Beats configuration |{agent} support