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

Is the @type elasticsearch_dynamic supported by fluent-operator ? #1400

Open
onap4105 opened this issue Nov 6, 2024 · 0 comments
Open

Is the @type elasticsearch_dynamic supported by fluent-operator ? #1400

onap4105 opened this issue Nov 6, 2024 · 0 comments

Comments

@onap4105
Copy link

onap4105 commented Nov 6, 2024

Is your feature request related to a problem? Please describe.

https://github.com/uken/fluent-plugin-elasticsearch
Dynamic configuration
NOTE: out_elasticsearch_dynamic will be planned to be marked as deprecated. Please don't use the new Fluentd configuration. This plugin is maintained for backward compatibility.

If you want configurations to depend on information in messages, you can use elasticsearch_dynamic. This is an experimental variation of the Elasticsearch plugin allows configuration values to be specified in ways such as the below:

<match my.logs.*>
@type elasticsearch_dynamic
hosts ${record['host1']}:9200,${record['host2']}:9200
index_name my_index.${Time.at(time).getutc.strftime(@logstash_dateformat)}
logstash_prefix ${tag_parts[3]}
port ${9200+rand(4)}
index_name ${tag_parts[2]}-${Time.at(time).getutc.strftime(@logstash_dateformat)}

Describe the solution you'd like

It would be nice to have logs end up in different indices based the namespace

Additional context

No response

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

No branches or pull requests

1 participant