-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
loki tenant_id_key eval is too late #6207
Labels
Comments
nokute78
added a commit
to nokute78/fluent-bit
that referenced
this issue
Oct 20, 2022
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
3 tasks
I sent a patch #6249. Could you check it ? |
Thanks, i've build you branch as |
edsiper
pushed a commit
that referenced
this issue
Oct 21, 2022
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
mgeriesa
pushed a commit
to mgeriesa/fluent-bit
that referenced
this issue
Oct 25, 2022
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com> Signed-off-by: Manal Geries <mgeriesa@gmail.com>
sumitd2
pushed a commit
to sumitd2/fluent-bit
that referenced
this issue
Feb 8, 2023
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com> Signed-off-by: root <root@sumit-acs.novalocal>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Describe the bug
In
loki
output theremove_keys
works ahead oftenant_id_key
, making it impossible to only send log message withdrop_single_key
. Thelabel_keys
also strip the key from message beforetenant_id_key
able to read it.To Reproduce
I have keys
log
with log message, andtenant_id
with desired id. I want to send event to loki having only clear message, and separate labels to this tenant, that why I'm removing all the keys and usedrop_single_key
.Unfortunately this leads to:
tenant_id
fromremove_keys
- data is being sent, but in loki it looks like:{labels} tenant_id=xxx log=aaa
Expected behavior
Log message above expected to look in loki as:
{labels} aaa
Your Environment
cr.fluentbit.io/fluent/fluent-bit:1.9.9
Additional context
I'm trying to use fluent-bit for multitenant loki logs per-namespace in k8s. But unfortunately upstream loki support seems to be too broken for that (see #2935 also).
I've found there is another fluent-bit with loki output: https://grafana.com/docs/loki/latest/clients/fluentbit/#configuration-options
But it only have a static tenant_id configuration (not per-event).
Having 2 different
fluent-bit loki
implementations seems strange.Will try to migrate to vector.dev, as per-docs it should be working there.
The text was updated successfully, but these errors were encountered: