Closed hp0620 closed 2 days ago
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)
This bug reported is created by Support as a result of the SFDC case - 01779437, instead of creating an SDH to Integration Team.
This is likely caused by logstash ECS compatibility mode (discussed offline).
I just realized that I used the wrong input file when I tested, which of course led to a behavior that's not the true representation of the ingestion.
Feeding a different file - https://github.com/elastic/integrations/blob/main/packages/panw_cortex_xdr/data_stream/alerts/_dev/test/pipeline/test-panw-xdr.log, I did not reproduce the issue the user was reporting. For this reason, I am closing this one.
Thank you, Dan for the quick response and apologies for the wrong alert!
Integration Name
Palo Alto Cortex XDR [panw_cortex_xdr]
Dataset Name
panw_cortex_xdr.alerts
Integration Version
1.29.0
Agent Version
8.15.3
Agent Output Type
logstash
Elasticsearch Version
8.15.3
OS Version and Architecture
Debian amd64 20.04.6 LTS (Focal Fossa)
Software/API Version
No response
Error Message
There are no errors in the log and the rest of the data gets ingested. However, in the ingested document, we can see, indicating the field was not correctly ingested, even though the
message
field was indeed ingested.Event Original
This is from the sample event - https://github.com/elastic/integrations/blob/main/packages/panw_cortex_xdr/data_stream/alerts/_dev/test/pipeline/test-panw-xdr.log-expected.json
What did you do?
Ingested a document using a single pipeline, to reproduce a behavior a user reported:
What did you see?
Was able to reproduce the same error that the user reported:
What did you expect to see?
No
field [message] already exists
errorAnything else?
The same message above was not detected from the
integration
data set.So checking the pipeline - logs-panw_cortex_xdr.alerts-1.29.0, , it looks like we are renaming the field,
, but as you can see in the sample data above, the
message
field is already there - https://github.com/elastic/integrations/blob/main/packages/panw_cortex_xdr/data_stream/alerts/_dev/test/pipeline/test-panw-xdr.log-expected.json#L51, so either the rename needs to send the
panw_cortex.xdr.name
to a different field or maybe delete the rename part?