This makes it possible to do more advanced monitoring and alerting later by using those attributes to filter, search and facet. We are also adding a tag that will control routing. regex - Fluentd match tag wildcard pattern matching In the Fluentd config file I have a configuration as such. The configuration file consists of the following directives: directives determine the output destinations, directives determine the event processing pipelines, directives group the output and filter for internal routing. All was working fine until one of our elastic (elastic-audit) is down and now none of logs are getting pushed which has been mentioned on the fluentd config. host_param "#{Socket.gethostname}" # host_param is actual hostname like `webserver1`. host_param "#{hostname}" # This is same with Socket.gethostname, @id "out_foo#{worker_id}" # This is same with ENV["SERVERENGINE_WORKER_ID"], shortcut is useful under multiple workers. and its documents. *> match a, a.b, a.b.c (from the first pattern) and b.d (from the second pattern). Access your Coralogix private key. Is it suspicious or odd to stand by the gate of a GA airport watching the planes? Tags are a major requirement on Fluentd, they allows to identify the incoming data and take routing decisions. The field name is service_name and the value is a variable ${tag} that references the tag value the filter matched on. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals. Wider match patterns should be defined after tight match patterns. Two other parameters are used here. Application log is stored into "log" field in the records. Do not expect to see results in your Azure resources immediately! Coralogix provides seamless integration with Fluentd so you can send your logs from anywhere and parse them according to your needs. fluentd-address option. By default, the logging driver connects to localhost:24224. @label @METRICS # dstat events are routed to