-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Suggestion: taggable values #440
Labels
Comments
+1 |
I suppose you _could_ accomplish with a custom field formatter, #1543 |
I'd agree that custom formatters would be the way to accomplish this, but really, even that requires joins in Elasticsearch todo correctly. I'm going to close this since the path forward on this one is field formatters. |
harper-carroll
pushed a commit
to harper-carroll/kibana
that referenced
this issue
Jul 11, 2016
…ghPut Revert "Add high through put"
This was referenced Mar 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be handy if we could tag values, for example:
I would tag the field "ClientIP", value "1.2.3.4" with "Office".
This way, when browsing through logfiles, I would easily see requests coming from our office for example.
This is something that is possible in Splunk and I found it really helpful at the time.
The text was updated successfully, but these errors were encountered: