
Hello Hans,
This feature is still in the pipeline as there seems to be a simple workaround for this use case. We can apply a static enrichment on the incoming logs by using “ GeoIp_source_address ” enrichment source.
However, this may not work for mapping the destination address traffic as the enrichment source matches the “source_address” not the “destination_address”
We cannot drill down right now as the logs are enriched only at the time of the search lookup when process command is used. This information will not persist in the actual logs if static enrichment is not configured.
We will update regarding this use case once this feature is available through dynamic enrichment.
1 comment