-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Telegraf Logparser - Response code: tag or field? #1479
Comments
👍 |
And this totally disables queries like |
oh, shoot, now I remember that is why I made it a field in the first place. I'll have to think if I want to change it back now |
This change basically invalidates the discussion here, due to comparators not working with tags (as mentioned by @Mikanoshi) |
if you want it as a field, you can change this by using your own custom log format:
|
Closing, use sparrc's technique to move the item to a tag if desired. |
Proposal:
Response Code should be tag in the logparser plugin
Current behavior:
It is a field
Desired behavior:
Is should be a tag
Use case: [Why is this important (helps with prioritizing requests)]
There are a limited number of variants for response code so it shouldn't increase series cardinality too much. It is very likely that you would want to use response code in a WHERE or GROUP BY query. This was initially proposed in the Google group and got a thumbs up from @beckettsean
The text was updated successfully, but these errors were encountered: