-
Notifications
You must be signed in to change notification settings - Fork 5.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
fix: Add metric name is a label with name "__name" to Loki output plugin #10001
Conversation
Thanks so much for the pull request! |
!signed-cla |
📦 Looks like new artifacts were built from this PR. Expand this list to get them here! 🐯Artifact URLs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @garciarodrigor, thanks for the nice PR. The code looks good. As I'm not a Loki expert I wonder what the effect of adding __name
is in terms of backward compatibility. Will existing users notice the change or will all their downstream pipeline continue working?
Hi @srebhan, the only concern I have about that, is the posible colition with some existing tags named |
Yeah and this might create an issue in InfluxDB because it will add another series, things that users may not want (e.g. if they have a large number of series already it will double that count). If I do understand you correctly, this is not the case with Loki. Is this correct? |
Loki store two different types of data: chunks and indexes, all labels (tags) will be stored in the indexes to speed up the queries, with out this missing dimesion we can't filter the data and we can incurr in some mistakes ex:
will be stored as
so, we can't run a query looking for a specific meassure or metric. Answering your question, loki don't know the concept of "series", it have labels indexed that point to the content called "chunk" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks @garciarodrigor for the PR and the helpful explanations! Btw, you do have selected a nice PR number... ;-P
Yeah, and a better Issue number too #10000 🥂, I haved this issue for a long time waiting for it, hahahaha |
This allows the user to specify the label name used to store the metric name. This label was added in influxdata#10001, but a user may not want this value in which case they could set it to an empty string or use some other customer value. fixes: influxdata#13146
This allows the user to specify the label name used to store the metric name. This label was added in influxdata#10001, but a user may not want this value in which case they could set it to an empty string or use some other customer value. fixes: influxdata#13146
This allows the user to specify the label name used to store the metric name. This label was added in influxdata#10001, but a user may not want this value in which case they could set it to an empty string or use some other customer value. fixes: influxdata#13146
This allows the user to specify the label name used to store the metric name. This label was added in influxdata#10001, but a user may not want this value in which case they could set it to an empty string or use some other customer value. fixes: influxdata#13146
Required for all PRs:
resolves #10000
Thi PR fix the loki output plugin, it add the metric name as a label with the name "__name", In order to filter data and improve queries performance in Loki.