Fluentd
1.0
1.0
  • Introduction
  • Overview
    • Life of a Fluentd event
    • Support
    • FAQ
    • Logo
    • fluent-package v5 vs td-agent v4
  • Installation
    • Before Installation
    • Install fluent-package
      • RPM Package (Red Hat Linux)
      • DEB Package (Debian/Ubuntu)
      • .dmg Package (macOS)
      • .msi Installer (Windows)
    • Install calyptia-fluentd
      • RPM Package (Red Hat Linux)
      • DEB Package (Debian/Ubuntu)
      • .dmg Package (macOS)
      • .msi Installer (Windows)
    • Install by Ruby Gem
    • Install from Source
    • Post Installation Guide
    • Obsolete Installation
      • Treasure Agent v4 (EOL) Installation
        • Install by RPM Package v4 (Red Hat Linux)
        • Install by DEB Package v4 (Debian/Ubuntu)
        • Install by .dmg Package v4 (macOS)
        • Install by .msi Installer v4 (Windows)
      • Treasure Agent v3 (EOL) Installation
        • Install by RPM Package v3 (Red Hat Linux)
        • Install by DEB Package v3 (Debian/Ubuntu)
        • Install by .dmg Package v3 (macOS)
        • Install by .msi Installer v3 (Windows)
  • Configuration
    • Config File Syntax
    • Config File Syntax (YAML)
    • Routing Examples
    • Config: Common Parameters
    • Config: Parse Section
    • Config: Buffer Section
    • Config: Format Section
    • Config: Extract Section
    • Config: Inject Section
    • Config: Transport Section
    • Config: Storage Section
    • Config: Service Discovery Section
  • Deployment
    • System Configuration
    • Logging
    • Signals
    • RPC
    • High Availability Config
    • Performance Tuning
    • Multi Process Workers
    • Failure Scenarios
    • Plugin Management
    • Trouble Shooting
    • Fluentd UI
    • Linux Capability
    • Command Line Option
    • Source Only Mode
    • Zero-downtime restart
  • Container Deployment
    • Docker Image
    • Docker Logging Driver
    • Docker Compose
    • Kubernetes
  • Monitoring Fluentd
    • Overview
    • Monitoring by Prometheus
    • Monitoring by REST API
  • Input Plugins
    • tail
    • forward
    • udp
    • tcp
    • unix
    • http
    • syslog
    • exec
    • sample
    • monitor_agent
    • windows_eventlog
  • Output Plugins
    • file
    • forward
    • http
    • exec
    • exec_filter
    • secondary_file
    • copy
    • relabel
    • roundrobin
    • stdout
    • null
    • s3
    • kafka
    • elasticsearch
    • opensearch
    • mongo
    • mongo_replset
    • rewrite_tag_filter
    • webhdfs
    • buffer
  • Filter Plugins
    • record_transformer
    • grep
    • parser
    • geoip
    • stdout
  • Parser Plugins
    • regexp
    • apache2
    • apache_error
    • nginx
    • syslog
    • ltsv
    • csv
    • tsv
    • json
    • msgpack
    • multiline
    • none
  • Formatter Plugins
    • out_file
    • json
    • ltsv
    • csv
    • msgpack
    • hash
    • single_value
    • stdout
    • tsv
  • Buffer Plugins
    • memory
    • file
    • file_single
  • Storage Plugins
    • local
  • Service Discovery Plugins
    • static
    • file
    • srv
  • Metrics Plugins
    • local
  • How-to Guides
    • Stream Analytics with Materialize
    • Send Apache Logs to S3
    • Send Apache Logs to Minio
    • Send Apache Logs to Mongodb
    • Send Syslog Data to Graylog
    • Send Syslog Data to InfluxDB
    • Send Syslog Data to Sematext
    • Data Analytics with Treasure Data
    • Data Collection with Hadoop (HDFS)
    • Simple Stream Processing with Fluentd
    • Stream Processing with Norikra
    • Stream Processing with Kinesis
    • Free Alternative To Splunk
    • Email Alerting like Splunk
    • How to Parse Syslog Messages
    • Cloud Data Logging with Raspberry Pi
  • Language Bindings
    • Java
    • Ruby
    • Python
    • Perl
    • PHP
    • Nodejs
    • Scala
  • Plugin Development
    • How to Write Input Plugin
    • How to Write Base Plugin
    • How to Write Buffer Plugin
    • How to Write Filter Plugin
    • How to Write Formatter Plugin
    • How to Write Output Plugin
    • How to Write Parser Plugin
    • How to Write Storage Plugin
    • How to Write Service Discovery Plugin
    • How to Write Tests for Plugin
    • Configuration Parameter Types
    • Upgrade Plugin from v0.12
  • Plugin Helper API
    • Plugin Helper: Child Process
    • Plugin Helper: Compat Parameters
    • Plugin Helper: Event Emitter
    • Plugin Helper: Event Loop
    • Plugin Helper: Extract
    • Plugin Helper: Formatter
    • Plugin Helper: Inject
    • Plugin Helper: Parser
    • Plugin Helper: Record Accessor
    • Plugin Helper: Server
    • Plugin Helper: Socket
    • Plugin Helper: Storage
    • Plugin Helper: Thread
    • Plugin Helper: Timer
    • Plugin Helper: Http Server
    • Plugin Helper: Service Discovery
  • Troubleshooting Guide
  • Appendix
    • Update from v0.12 to v1
    • td-agent v2 vs v3 vs v4
Powered by GitBook
On this page
  • Installation
  • Example Configuration
  • Plugin Helpers
  • Parameters
  • @type (required)
  • host (optional)
  • port (optional)
  • hosts (optional)
  • user, password (optional)
  • scheme (optional)
  • path (optional)
  • index_name (optional)
  • logstash_format (optional)
  • logstash_prefix (optional)
  • Miscellaneous
  • Common Output / Buffer parameters
  • Troubleshooting
  • Further Reading

Was this helpful?

  1. Output Plugins

opensearch

PreviouselasticsearchNextmongo

Last updated 3 years ago

Was this helpful?

The out_opensearch Output plugin writes records into OpenSearch. By default, it creates records using which performs multiple indexing operations in a single API call. This reduces overhead and can greatly increase indexing speed. This means that when you first import records using the plugin, records are not immediately pushed to OpenSearch.

Records will be sent to OpenSearch when the chunk_keys condition has been met. To change the output frequency, please specify the time in chunk_keys and specify timekey value in the configuration.

This document does not describe all the parameters. For details, refer to the Further Reading section.

Installation

Since out_opensearch has been included in the alternative distribution of calyptia-fluentd since v1.3.4, calyptia-fluentd users do not need to install it manually.

If you have installed Fluentd without calyptia-fluentd, please install this plugin using fluent-gem or td-agent-gem (for td-agent users):

$ fluent-gem install fluent-plugin-opensearch
$ td-agent-gem install fluent-plugin-opensearch

Example Configuration

Here is a simple working configuration for OpenSearch instance that is running on localhost:

<match my.logs>
  @type opensearch
  host localhost
  port 9200
  logstash_format true
</match>

For more details on each option, read the section on .

Plugin Helpers

Parameters

@type (required)

This option must be always opensearch.

host (optional)

The hostname of your OpenSearch node (default: localhost).

port (optional)

The port number of your OpenSearch node (default: 9200).

hosts (optional)

If you want to connect to more than one OpenSearch nodes, specify this option in the following format:

hosts host1:port1,host2:port2,host3:port3
# or
hosts https://customhost.com:443/path,https://username:password@host-failover.com:443

If you use this option, the host and port options are ignored.

user, password (optional)

The login credentials to connect to the OpenSearch node (default: nil):

user fluent
password mysecret

scheme (optional)

Specify https if your OpenSearch endpoint supports SSL (default: http).

path (optional)

The REST API endpoint of OpenSearch to post write requests (default: nil).

index_name (optional)

The index name to write events to (default: fluentd).

This option supports the placeholder syntax of Fluentd plugin API. For example, if you want to partition the index by tags, you can specify it like this:

index_name fluentd.${tag}

Here is a more practical example which partitions the OpenSearch index by tags and timestamps:

index_name fluentd.${tag}.%Y%m%d

Time placeholder needs to set up tag and time in chunk_keys. Also, it needs to specify timekey for time slice of chunk:

<buffer tag, time>
  timekey 1h # chunks per hours ("3600" also available)
</buffer>

logstash_format (optional)

If true, Fluentd uses the conventional index name format logstash-%Y.%m.%d (default: false). This option supersedes the index_name option.

@log_level option

The @log_level option allows the user to set different levels of logging for each plugin.

Supported log levels: fatal, error, warn, info, debug, trace.

logstash_prefix (optional)

The logstash prefix index name to write events when logstash_format is true (default: logstash).

Miscellaneous

You can use %{} style placeholders to escape for URL encoding needed characters.

Valid configuration:

user %{demo+}
password %{@secret}

Valid configuration:

hosts https://%{j+hn}:%{passw@rd}@host1:443/elastic/,http://host2

Invalid configuration:

user demo+
password @secret

Common Output / Buffer parameters

For common output / buffer parameters, please check the following articles:

Troubleshooting

Further Reading

For more information about buffer options checkout the .

Please see the for further details.

Please refer to the section.

If this article is incorrect or outdated, or omits critical information, please . is an open-source project under . All components are available under the Apache 2 License.

event_emitter
compat_parameters
Buffer Section Configuration
logging article
Output Plugin Overview
Buffer Section Configuration
OpenSearch's troubleshooting
fluent-plugin-opensearch
let us know
Fluentd
Cloud Native Computing Foundation (CNCF)
bulk api
Parameters