We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello @yokawasa,
Thank you for maintaining this plugin.
Some advice on how to achieve the following use case would be appreciated.
What I am tryint to achieve is, to somehow capture the content of "*" in the <match> tag, and to apply it to docdb_collection, such as the following.
<match>
docdb_collection
<match tenant.*> # <------ Want to access * @type documentdb @log_level info docdb_endpoint https://abc.documents.azure.com:443 docdb_account_key abc== docdb_database tenants docdb_collection ${tag} # <------ To use here...
Above example did not work, and resulted in creating a container called ${tag} in my Cosmos DB instance.
${tag}
I was able to achieve this by using fluent-plugin-forest, however, the author of the plugin mentions that:
NOTE: This plugin will not be updated: Use Fluentd v0.14 native API to handle tags.
Is there a way to achieve this in fluent-plugin-documentdb natively?
fluent-plugin-documentdb
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello @yokawasa,
Thank you for maintaining this plugin.
Some advice on how to achieve the following use case would be appreciated.
What I am tryint to achieve is, to somehow capture the content of "*" in the
<match>
tag, and to apply it todocdb_collection
, such as the following.Above example did not work, and resulted in creating a container called
${tag}
in my Cosmos DB instance.I was able to achieve this by using fluent-plugin-forest, however, the author of the plugin mentions that:
Is there a way to achieve this in
fluent-plugin-documentdb
natively?The text was updated successfully, but these errors were encountered: