You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
28
+
% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
29
+
% These IDs are from content that I'm not including on this current page. I've resolved them by changing the internal links to anchor links where needed. - Wajiha
Copy file name to clipboardExpand all lines: raw-migrated-files/ingest-docs/fleet/beats-agent-comparison.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,8 +23,8 @@ This article summarizes the features and functionality you need to be aware of b
23
23
The following steps will help you determine if {{agent}} can support your use case:
24
24
25
25
1. Determine if the integrations you need are supported and Generally Available (GA) on {{agent}}. To find out if an integration is GA, see the [{{integrations}} quick reference table](https://docs.elastic.co/en/integrations/all_integrations).
26
-
2. If the integration is available, check [Supported outputs](../../../manage-data/ingest/tools.md#supported-outputs-beats-and-agent) to see whether the required output is also supported.
27
-
3. Review [Capabilities comparison](../../../manage-data/ingest/tools.md#additional-capabilities-beats-and-agent) to determine if any features required by your deployment are supported. {{agent}} should support most of the features available on {{beats}} and is updated for each release.
26
+
2. If the integration is available, check [Supported outputs](#supported-outputs-beats-and-agent) to see whether the required output is also supported.
27
+
3. Review [Capabilities comparison](#additional-capabilities-beats-and-agent) to determine if any features required by your deployment are supported. {{agent}} should support most of the features available on {{beats}} and is updated for each release.
28
28
29
29
If you are satisfied with all three steps, then {{agent}} is suitable for your deployment. However, if any steps fail your assessment, you should continue using {{beats}}, and review future updates or contact us in the [discuss forum](https://discuss.elastic.co/).
30
30
@@ -67,7 +67,7 @@ The following table shows the outputs supported by the {{agent}} in 9.0.0-beta1:
67
67
|[Project paths](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-path.html)| {{agent}} configures these paths to provide a simpler and more streamlinedconfiguration experience. |
68
68
|[External configuration file loading](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-configuration-reloading.html)| Config is distributed via policy. |
69
69
|[Live reloading](https://www.elastic.co/guide/en/beats/filebeat/current/_live_reloading.html)| Related to the config file reload. |
70
-
|[Outputs](https://www.elastic.co/guide/en/beats/filebeat/current/configuring-output.html)| Configured through {{fleet}}. See [Supported outputs](../../../manage-data/ingest/tools.md#supported-outputs-beats-and-agent). |
70
+
|[Outputs](https://www.elastic.co/guide/en/beats/filebeat/current/configuring-output.html)| Configured through {{fleet}}. See [Supported outputs](#supported-outputs-beats-and-agent). |
|[{{ilm-cap}}](https://www.elastic.co/guide/en/beats/filebeat/current/ilm.html)| Enabled by default although the Agent uses [data streams](https://www.elastic.co/guide/en/fleet/current/data-streams.html). |
73
73
|[{{es}} index template loading](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-template.html)| No longer applicable |
0 commit comments