karmada-io
/
karmada
mirror of https://github.com/karmada-io/karmada.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1192 from Rains6/doc 

modify filebeat doc reference
This commit is contained in:
karmada-bot 2021-12-30 11:26:40 +08:00 committed by GitHub
parent e8a206640e db05a507ae
commit 075bfc97ba
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/working-with-filebeat.md
View File

@ -1,6 +1,6 @@
# Use Filebeat to collect logs of Karmada member clusters
[Filebeat](https://www.elastic.co/cn/beats/filebeat) is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to [Elasticsearch](https://www.elastic.co/products/elasticsearch) or [Logstash](https://www.elastic.co/products/logstash) for indexing.
[Filebeat](https://github.com/elastic/beats/tree/master/filebeat) is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to [Elasticsearch](https://www.elastic.co/products/elasticsearch) or [kafka](https://github.com/apache/kafka) for indexing.
This document gives an example to demonstrate how to use the `Filebeat` to collect logs of karmada member clusters.
@ -14,7 +14,7 @@ hack/local-up-karmada.sh
## Start Filebeat
1. Create resource objects of Filebeat, the content is as follows. You can specify a list of inputs in the `filebeat.inputs` section of the `filebeat.yml`. Inputs specify how Filebeat locates and processes input data. also you can configure Filebeat to write to a specific output by setting options in the `Outputs` section of the `filebeat.yml` config file. The example will collect the log information of each container and write the collected logs to a file. More detailed information about the input and output configuration, please refer to: https://www.elastic.co/guide/en/beats/filebeat/current/configuring-howto-filebeat.html
1. Create resource objects of Filebeat, the content is as follows. You can specify a list of inputs in the `filebeat.inputs` section of the `filebeat.yml`. Inputs specify how Filebeat locates and processes input data. also you can configure Filebeat to write to a specific output by setting options in the `Outputs` section of the `filebeat.yml` config file. The example will collect the log information of each container and write the collected logs to a file. More detailed information about the input and output configuration, please refer to: https://github.com/elastic/beats/tree/master/filebeat/docs
```
apiVersion: v1
@ -237,4 +237,4 @@ hack/local-up-karmada.sh
## Reference
- https://github.com/elastic/beats/tree/master/filebeat
- https://www.elastic.co/guide/en/beats/filebeat/current/index.html
- https://github.com/elastic/beats/tree/master/filebeat/docs