https://github.com/sonots/fluent-plugin-copy_ex

Fluentd out_copy extension
https://github.com/sonots/fluent-plugin-copy_ex

fluentd-output-plugin fluentd-plugin multi-workers-ready multioutput v12 v14

Last synced: 2 months ago
JSON representation

Fluentd out_copy extension

• Host: GitHub
• URL: https://github.com/sonots/fluent-plugin-copy_ex
• Owner: sonots
• License: other
• Created: 2014-04-30T05:49:08.000Z (over 10 years ago)
• Default Branch: master
• Last Pushed: 2017-11-24T16:00:55.000Z (about 7 years ago)
• Last Synced: 2024-09-14T23:52:38.256Z (3 months ago)
• Topics: fluentd-output-plugin, fluentd-plugin, multi-workers-ready, multioutput, v12, v14
• Language: Ruby
• Size: 21.5 KB
• Stars: 6
• Watchers: 1
• Forks: 5
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# fluent-plugin-copy_ex

Fluentd out\_copy extension

## What is this for?

Think of `out_copy` configuration as followings:

```apache

  type copy

  

    type plugin1

  

  

    type plugin2

  

```

In the current Fluentd, when plugin1 raises an error internally, the chain is broken and the plugin2 is not executed. 

The `out_copy_ex` supplies `ignore_error` option so that it will not break the chain and the plugin2 is executed. 

See https://github.com/fluent/fluentd/pull/303 for discussions. 

## Configuration

```apache

  type copy_ex

  

    type plugin1

  

  

    type plugin2

  

```

## Parameters

Basically same with out\_copy plugin. See http://docs.fluentd.org/articles/out_copy

    

## Contributing

1. Fork it

2. Create your feature branch (`git checkout -b my-new-feature`)

3. Commit your changes (`git commit -am 'Add some feature'`)

4. Push to the branch (`git push origin my-new-feature`)

5. Create new [Pull Request](../../pull/new/master)

## ChangeLog

See [CHANGELOG.md](CHANGELOG.md) for details.

## Copyright

* Copyright (c) 2014- Naotoshi Seo

* See [LICENSE](LICENSE) for details.