Fluentd: event forwarding to Elasticsearch lasts when using the copy plugin

I configure my fluentD configuration and for certain events, I need to push them to both the log and elasticsearch log. I use the copy plugin for this, but I see a significant difference in the time sent by calling fluentD to return - the time spent on the test POST call made through the postman. It will take about 5 seconds if I use elasticsearch matching inside copy vs <1s to directly match elasticsearch. I am using the following configuration.

<match testapp.elastic> @type elasticsearch host localhost port 9200 index_name fluentdtest type_name fluentdtest </match> #Common match for loggly and mongo <match logapp.**> type copy <store> @type elasticsearch host localhost port 9200 index_name fluentdtest type_name fluentdtest </store> <store> type forest subtype loggly <template> loggly_url ##myurl##/tag/${tag} </template> </store> </match> 
+8
plugins elasticsearch fluentd
source share

No one has answered this question yet.

See related questions:

51
Java ElasticSearch Not all configured nodes are available
0
Create a dynamic index name using fluentd and fluent-plugin-elasticsearch
0
Using id_key with fluentd / elasticsearch support
0
How to access elasticsearch from Linux Guest (Virtualbox) to the OSX host?
0
Fluentd: How to solve the problem with the fluentd forward plugin?
0
Mongo-Connector cannot connect MongoDB Replica for Elasticsearch
0
Flumend and Kibana
0
fluentd-plugin-gelf launches DNS name resolution error
0
Mongo-connector error on ubuntu 14.14
0
create ElasticSearch river for MongoDb replication

All Articles