-
Notifications
You must be signed in to change notification settings - Fork 125
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
User-agent extractor/function #1483
Comments
Should this perhaps rather be a tremor function instead of a extractor? We do support all the needed logic already and can avoid adding one-of-a-kind extractors this way. |
Yep - a function would be fine too - updating issue |
There are many standard headers that we could have util functions for - like repeated headers, content-type/mime, accept ... |
I love that idea, a http module with the common logic would be absolutely great! |
And it would make for great first issues too :D |
Each connector should probably have its own module of utilities - it worked well for |
Does this problem still need to be solved? I'd like to try it out if I can. |
Heya, yes it does and it should be a good issue to start with, I'll assign it to you, feel free to hop by https://chat.tremor.rs if you need any help or pointers :) |
heya @tobehardest do you need any help from us? |
unassigning this again due to lack of response |
Describe the problem you are trying to solve
As a user, I would like an extractor/function to dissect HTTP user agent headers
Describe the solution you'd like
Something along the lines of logstash's user-agent plugin: https://www.elastic.co/guide/en/logstash/current/plugins-filters-useragent.html
The text was updated successfully, but these errors were encountered: