-
Notifications
You must be signed in to change notification settings - Fork 614
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
Hostname Artifact #900
Comments
I can understand the difference you are talking about, but I don't see the question :) You can add a |
Am I misunderstanding something? I thought Cortex really only supported the built in data types? |
No, Cortex can even run an analyzer on So replace |
Ah, I see its more of a Cortex issue.. But if Cortex were to add hostname then I feel like it shoul dbe a standard Hive data type. |
So you're saying cortex doesn't really care and as long as i set whatever i want as the data types for the analyzer... then it will work? If this is the case then you have made me very happy :) |
Yes |
That works for me! Thanks! |
Request Type
Feature Request
Problem Description
hostname is probably a common artifact type and it would be useful to be able to mark something as hostname that could also get passed to cortex to have analyzers run on it.
i dont like to use fqdn for this as hostnames are usually internal, so i wouldnt want a fqdn analyzer to process this as an fqdn, instead an analyzer that is internal that would look up info about a hostname
The text was updated successfully, but these errors were encountered: