Closed Danouchka closed 2 months ago
Pinging @elastic/integrations (Team:Integrations)
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)
The removal of event.dataset is part of https://github.com/elastic/integrations/issues/8185 and I suspect that the geoip issue is due to configuration since this is configurable.
The issue is that event.dataset is used as a partition field in the default ML jobs for Log Categorization in Observability The fact that it is disappearing may be an issue
For the geoip configuration issue, seems the integration upgrade miss the configuration value. I reenabled the toggle (switch off et switch on again ) and this works again.
But the event.dataset should be kept for the reasons I have mentionned above
The change is in line with the planned deprecation and retirement plan in #8185 and is stage 3. (perhaps with one exception; I'm not sure if the fleet changes that are indicated there to have happened actually did /cc @nimarezainia). I've marked the PR into the plan, but left it as not completed. The removal of event.dataset
should not prevent you from partitioning the documents; data_stream.dataset
provide the same information, which is why event.dataset
was removed.
If you absolutely need to use event.dataset
in the short term, you can change the configuration for "Map root Packetbeat fields to ECS" to false, though note that the option is planned to be removed completely in six months.
@efd6 no unfortunately I missed this ping. I don;t think we made any changes in the integrations/fleet in this regard. will follow up in the original issue.
Thank you ! I think we can close the ticket. Just to be aware, might switch off and on again the GeoIP resolution configuration toggle
Integration Name
Network Packet Capture [network_traffic]
Dataset Name
event.dataset is missing
Integration Version
1.32.0
Agent Version
8.15.0
Agent Output Type
elasticsearch
Elasticsearch Version
8.15.0
OS Version and Architecture
Elasticsearch in Elastic Cloud. Agents are on Centos7 and Debian 11
Software/API Version
No response
Error Message
Since I have upgraded the integration to 1.32.0 on Friday August 30th, I see that records produced by this integration does not have the event.dataset field and GeoIP resolution for source.ip and destination.ip is missing (specifically for records related to data_stream.dataset :"network_traffic.flow" )
Event Original
Exemple of produced record
What did you do?
Nothing special , just upgraded the integration
What did you see?
event.dataset is missing no GeoIP resolution for source.ip and destination.ip as it used to be
What did you expect to see?
I expect to have the field event.dataset properly filled and source.ip and destination.ip to be geoIP resolved
ex of records before it was broken
Anything else?
No response