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
{{ message }}
This repository was archived by the owner on Sep 21, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Data shipper for the Elastic Agent - a single, unified way to add monitoring for
6
6
other types of data to a host.
7
7
8
8
The data shipper is a new process in the Elastic agent system designed to centralize local data
9
-
processing, queueuing, and publishing to the target output (Elasticsearch, Logstash, etc.).
9
+
processing, queueing, and publishing to the target output (Elasticsearch, Logstash, etc.).
10
10
11
11
The data shipper is a part of a larger effort to rearchitect the Elastic agent. In the initial Elastic
12
12
agent architecture each underlying data collector (e.g. Filebeat) was required to implement its own
@@ -30,10 +30,20 @@ Data shipper clients must implement the shipper [gRPC API](https://github.com/el
30
30
The reference client is the [Beats shipper output](https://github.com/elastic/beats/tree/main/libbeat/outputs/shipper), which is
31
31
used by Beats like Filebeat and Metricbeat when they are started by Elastic agent integrations.
32
32
33
-
Data shipper support in the Elastic Agent is under active development. The shipper currently depends on a running Elastic agent instance to
34
-
start but it will soon be possible to run the shipper in standalone mode for development: https://github.com/elastic/elastic-agent-shipper/issues/83
33
+
Data shipper support in the Elastic Agent is under active development.
35
34
36
-
The [reference shipper configuration file](https://github.com/elastic/elastic-agent-shipper/blob/main/elastic-agent-shipper.yml) defines the available
35
+
The shipper currently can be run in 2 modes:
36
+
37
+
* Under Elastic agent (managed mode): the main mode for running in production environments
38
+
* Using a local config file (unmanaged mode): is supposed to be used for local development and testing
39
+
40
+
To run the shipper in the unmanaged mode use this flag on the built binary:
41
+
42
+
```sh
43
+
./elastic-agent-shipper run -c elastic-agent-shipper.yml
44
+
```
45
+
46
+
Where `elastic-agent-shipper.yml` is a path to a local configuration file. The [reference shipper configuration file](https://github.com/elastic/elastic-agent-shipper/blob/main/elastic-agent-shipper.yml) defines the available
0 commit comments