Fix system tests using logstash for ingest only write one event per data stream #2117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change addresses the issue elastic/integrations#8530
Reported issue
When experimenting with using
stack.logstash_enabled
and running thepanw
system tests, only one event is indexed for any data stream checked:Using Logstash for ingest:
Expected:
Logstash logs showing version conflict errors for every other missing event:
{"type"=>"version_conflict_engine_exception", "reason"=>"[%{[@metadata][_ingest_document][id]}]: version conflict, document already exists (current version [9])", "index_uuid"=>"kHyWSHBOSfqankKX9IDHeg", "shard"=>"0", "index"=>".ds-logs-panw.panos-ep-2023.11.16-000001"}
Full error
Problem details
I found that the
document_id
is not getting resolved, like it is expected in this template:https://github.com/elastic/elastic-package/blob/main/internal/stack/_static/logstash.conf.tmpl#L31
when the
_ingest_document
is missing.So first document was created with:
and the remaining documents had the same string as the id. That's why only one document was stored, and rest were getting document version conflicts.
Solution
The solution is to add the condition checking for
[@metadata][_ingest_document][id]
existance and alternate the output configuration.