Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.14] Remove review comments and add missing support statement (#932) #934

Merged
merged 1 commit into from
Jul 30, 2021
Merged

[7.14] Remove review comments and add missing support statement (#932) #934

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 1 addition & 18 deletions docs/en/ingest-management/beats-agent-comparison.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,23 +1,13 @@
[[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
{es}. Elastic provides separate {beats} for different types of data, such as
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}.

Expand Down Expand Up @@ -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]
Expand All @@ -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}
Expand Down Expand Up @@ -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
Expand Down