Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature - support section arguments #131

Conversation

simonasr
Copy link

@simonasr simonasr commented Jul 16, 2019

Hi ;)
These changes will let you configure section parameters like <buffer tag, key1, key2> (solves #118)
For example: you can use this code to configure ElasticSearch output:

td_agent_match 'output_es' do
  type 'elasticsearch'
  tag 'logs.**'
  parameters(
    hosts: 'localhost:9200',
    logstash_prefix: 'fluent-${key1}.${key2}',
    'buffer tag, key1, key2' => {
      timekey: '1d'
    }
  )
end

This code will result configuration which will route logs to different indices based on specific keys in message.

<match logs.**>
  @type elasticsearch
  index_name elastic.${key1}.${key2}
  <buffer tag, key1, key2>
    timekey 1d
  </buffer>
</match>

More information related to section parameters:

@simonasr simonasr force-pushed the feature/support-section-arguments branch from d6f8bf8 to 2619459 Compare July 17, 2019 08:22
@simonasr simonasr force-pushed the feature/support-section-arguments branch from 2619459 to 0de252b Compare September 17, 2019 11:03
@simonasr
Copy link
Author

@yyuu - any chance this PR gets reviewed? : 🙏 😉

@scalp42
Copy link
Contributor

scalp42 commented Jul 2, 2020

@simonasr would it fix #142 as well?

@yyuu any chance to get this reviewed and merged? 👍

@evandam
Copy link

evandam commented Jul 22, 2020

Hi @yyuu and @simonasr, any updates on getting this merged? It would be a big help for us!

@simonasr
Copy link
Author

@simonasr would it fix #142 as well?

@scalp42 it should.

But this repository looks abandoned 😢

@scalp42
Copy link
Contributor

scalp42 commented Dec 14, 2020

@yyuu should we fork it?

@marijus-ravickas
Copy link

Howdy guys, any news on this PR merge?

@simonasr simonasr closed this Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants