The @fluent-org/loggerarrow-up-right library is used to post records from Node.js applications to Fluentd.
This article explains how to use it.
NOTE: The previous NPM package, fluent-loggerarrow-up-right has been deprecated in favor of @fluent-org/logger.
Basic knowledge of Node.js and NPM
Basic knowledge of Fluentd
Installing Fluentd
Please refer to the following document to install Fluentd:
Modifying the Config File
Configure Fluentd to use the forward input plugin as its data source:
Copy <source>
@type forward
port 24224
</source>
<match fluentd.test.**>
@type stdout
</match> Restart agent after configuring.
Using @fluent-org/logger
Obtaining the Most Recent Version
The most recent version of @fluent-org/logger can be found herearrow-up-right .
A Sample Application
Here is a sample Expressarrow-up-right app using @fluent-org/logger:
Use npm to install dependencies locally:
This is a simple web app:
Run the app and go to http://localhost:3000/ in your browser to send the logs to Fluentd:
The logs should be output to /var/log/td-agent/td-agent.log or the standard output of the Fluentd process via stdout output plugin.
Production Deployments
Various output plugins are available for writing records to other destinations:
List of Plugin References
High-Availability Configurations of Fluentd
For high-traffic websites (more than 5 application nodes), we recommend using the high-availability configuration for td-agent. This will improve the reliability of data transfer and query performance.
Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for td-agent.
If this article is incorrect or outdated, or omits critical information, please let us knowarrow-up-right . Fluentdarrow-up-right is an open-source project under Cloud Native Computing Foundation (CNCF)arrow-up-right . All components are available under the Apache 2 License.