MongoDB is a source-available cross-platform document-oriented database program. Fluentd is an open source data collector and a great option because of its flexibility. This integration lets you send logs from your MongoDB instances to your Logz.io account using Fluentd.

Step by step

Before you begin, you’ll need:

  • MongoDB installed on your host
  • Ruby 2.4+ and Ruby-dev
Configure MongoDB to write logs to a file

In the configuration file of your MongoDB instance, set the database to write logs to a file. You can skip this step if this has already been configured on your MongoDB host.

To do this, add the following to your MongoDB configuration file:

systemLog:
   destination: file
   path: "<<MONGODB-FILE-PATH>>"
   logAppend: true
  • Replace <<MONGODB-FILE-PATH>> with the path to the log file, for example, /var/log/mongodb/mongod.log.

Make sure Fluend can read from the MongoDB log file. You can set this as follows:

On macOS and Linux
sudo chmod 604 <<MONGODB-FILE-PATH>>
  • Replace <<MONGODB-FILE-PATH>> with the path to the MongoDB log file.
On Windows

Enable the read access in the file properties.

Install Fluentd
gem install fluentd
fluentd --setup ./fluent

This command creates a directory called fluent where we will create the configuration file and Gemfile.

Create a Gemfile for Fluentd

In your preffered directory, create a Gemfile with the following content:

source "https://rubygems.org"
# You can use fixed version of Fluentd and its plugins
# Add plugins you want to use
gem "fluent-plugin-logzio", "0.0.21"
gem "fluent-plugin-record-modifier"
Configure Fluentd with Logz.io output

Add this code block to your Fluent configuration file (fluent.conf by default).

See the configuration parameters below the code block.👇

# To ignore fluentd logs
<label @FLUENT_LOG>
  <match fluent.*>
    @type null
  </match>
</label>
# Tailing mongodb logs
<source>
  @type tail
  @id mongodb_logs
  path <<MONGODB-FILE-PATH>>
  # If you're running on windows, change the pos_file to a Windows path
  pos_file /var/log/fluentd-mongodb.log.pos
  tag logzio.mongodb.*
  read_from_head true
  <parse>
    @type json
  </parse>
</source>
# Parsing the logs
<filter logzio.mongodb.**>
  @type record_modifier
  <record>
    type  mongodb-fluentd
    message ${record["msg"]}
    mongodb_timestamp ${record["t"]["$date"]}
    log_id ${record["id"].to_s}
  </record>
  remove_keys msg,t,id
</filter>
# Sending logs to Logz.io
<match logzio.mongodb.**>
  @type logzio_buffered
  endpoint_url https://<<LISTENER-HOST>>:8071?token=<<LOGZIO-SHIPPING-TOKEN>>
  output_include_time true
  output_include_tags true
  http_idle_timeout 10
  <buffer>
      @type memory
      flush_thread_count 4
      flush_interval 3s
      chunk_limit_size 16m      # Logz.io bulk limit is decoupled from chunk_limit_size. Set whatever you want.
      queue_limit_length 4096
  </buffer>
</match>
Parameters
Parameter Description
<<LOGZIO-SHIPPING-TOKEN>> Your Logz.io log shipping token directs the data securely to your Logz.io Log Management account. The default token is auto-populated in the examples when you’re logged into the Logz.io app as an Admin. Manage your tokens.
<<LISTENER-HOST>> Replace <<LISTENER-HOST>> with the host for your region. For example, listener.logz.io if your account is hosted on AWS US East, or listener-nl.logz.io if hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071.
<<MONGODB-FILE-PATH>> Path to the log file of your MongoDB.
endpoint_url A url composed of your Logz.io region’s listener URL, account token, and log type. Replace <<LISTENER-HOST>> with the host for your region. For example, listener.logz.io if your account is hosted on AWS US East, or listener-nl.logz.io if hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071. Replace <<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.
output_include_time To add a timestamp to your logs when they’re processed, true (recommended). Otherwise, false.
output_include_tags To add the fluentd tag to logs, true. Otherwise, false. If true, use in combination with output_tags_fieldname.
output_tags_fieldname If output_include_tags is true, sets output tag’s field name. The default is fluentd_tag
http_idle_timeout Time, in seconds, that the HTTP connection will stay open without traffic before timing out.
Run Fluentd
fluentd -c ./fluent.conf --gemfile ./Gemfile
Check Logz.io for your logs

Give your logs some time to get from your system to ours, and then open Open Search Dashboards. You can search for type:mongodb-fluentd to filter for your MongoDB logs. Your logs should be already parsed thanks to the Logz.io preconfigured parsing pipeline.

If you still don’t see your logs, see log shipping troubleshooting.