Parse also the port from log sources#9460
Conversation
105e70e to
7ee4167
Compare
|
I'm wondering if we should call the filed This also has an affect on #9435 |
Not sure, I guess this is like the usual discussion about having a field that accepts hostnames or ip. In this case I think this is always an IP, but not sure if under some circunstances this can make inverse lookups. In any case we can think what to do with the host/ip field in another PR and keep this one only for the port. |
|
If we introduce |
|
Oh, you mean using |
|
For the discussion around For the port: yes, if we use address, I would not add it as a separate field. I see this more as meta information then information that is often queried on. |
|
Ok, I'm fine with using |
|
@jsoriano Yes, should go in latest tonight. |
|
Created #9487 to go for |
If source is a host, and it contains ip and port, it fails
to index after #8902 with an error like:
It happens at least with the syslog input.
This change parses the source in network inputs so if it
contains a port it is also added to the event in a separate
field.