-
Notifications
You must be signed in to change notification settings - Fork 97
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 it possible to define custom input tag for fluentbit configs? #44
Comments
The tag is set by FireLens and is always in the format of {container name}-firelens-{task ID}. There is no way to change this directly. You can however use Fluent Bit plugins to change the tag after the input stage. You can use a filter to change the tag: https://docs.fluentbit.io/manual/pipeline/filters/rewrite-tag Fluentd has a rewrite tag filter as well, so you could also change the tag in your Fluentd aggregator. |
I think Wesley's suggestion for using |
is this information in any documentation ? It would help me a lot to know where to find this kind of information. |
Hi,
I have usecase where I'm moving my infrastructure to ECS Fargate and out like to define custom input configs.
In my task definition, I'm launching two containers:
app
andfluentbit
. Theapp
container uses firelens to forward stdout logs tofluentbit
, which then forwards the logs to fluentd aggregators.Additionally, I create a custom output config file at
/fluent-bit/configs/custom-output.conf
in fluentbit image with the following content:The
Host
andPort
are replaced usingentrypoint.sh
script(both are passed to task definition as environment variables).The logs that get forwarded have a customer index/tag which starts with service name defined in task definition.
Task definition
Sample log
From the above example, the logs are sent with Tag as service name
nginx-web-45
.So the question here is:
Is possible to also have a custom input config? if yes, is it possible to have custom input
Tag
?Any guidance would be much appreciated.
thanks in advance!
The text was updated successfully, but these errors were encountered: