flylan opened a new issue, #538: URL: https://github.com/apache/apisix-helm-chart/issues/538
Refer to this article on the official blog: https://apisix.apache.org/zh/blog/2023/02/28/transforming-logs-for-ingestion-into-your-observability-stack/#elasticsearch-logger Apisix provides the Elasticsearch logger plugin, which can directly save logs to Elasticsearch without deploying filebeat. However, saving logs directly to Elasticsearch has a significant drawback, which is that if Elasticsearch hangs or responds slowly, it can seriously affect the Apisix gateway. Therefore, most scenarios do not directly save logs to Elasticsearch on the application side, and instead adopt the method of writing logs to a file, ultimately collecting logs through software such as FileBeat, Fluentd, or Loggie, and then synchronizing them to Elasticsearch to achieve asynchronous log writing However, it is relatively easy to configure software such as FileBeat to collect logs on traditional kvm or physical servers. However, configuring FileBeat to collect K8s container logs can be cumbersome. Traditional methods include sidecars or daemonset, which have a strong intrusion into the help view of Apisix. Collecting logs through daemonset incurs higher maintenance costs. Do I consider providing relevant help configurations for log collection in the Apisix help view? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
