-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Zeek] Add additional data sets #3340
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
packages/zeek/data_stream/known_certs/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
/test |
@efd6 can we retest |
/test |
🌐 Coverage report
|
/test |
fixed the test error. Ready to retest. |
/test |
@efd6 Any idea about the error from Elastic Machine or from Jenkins |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incidental to looking into the issue:
--- Test results for package: zeek - START ---
FAILURE DETAILS:
zeek/dns test-dns.log:
[0] parsing field value failed: the IP "40.126.31.143" is not one of the allowed test IPs (see: https://github.com/elastic/elastic-package/blob/main/internal/fields/_static/allowed_geo_ips.txt)
zeek/known_certs test-known_certs.log:
[0] parsing field value failed: field "event.kind"'s value "info" is not one of the allowed values (alert, enrichment, event, metric, state, pipeline_error, signal)
zeek/known_hosts test-known_hosts.log:
[0] parsing field value failed: field "event.kind"'s value "info" is not one of the allowed values (alert, enrichment, event, metric, state, pipeline_error, signal)
zeek/known_services test-known_services.log:
[0] parsing field value failed: field "event.kind"'s value "info" is not one of the allowed values (alert, enrichment, event, metric, state, pipeline_error, signal)
zeek/software test-software.log:
[0] parsing field value failed: field "event.kind"'s value "info" is not one of the allowed values (alert, enrichment, event, metric, state, pipeline_error, signal)
packages/zeek/data_stream/known_certs/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
The non-progress issue comes down to the absence of terminating new-lines in the test inputs. There are bunch of other inputs that suffer the same issue, but these all have more than one test line, so they pass because only a single event is required to allow a system test to pass (they would have been found if this were in place). |
🤦♂️ ya I've had this issue before, good catch. I'll fix this in the AM and then I think we should be good. |
The other inputs that have the issue are
|
@efd6 fixed |
/test |
@efd6 I think i got it now 🤦 |
That will fix the non-progress, but |
/test |
The |
packages/zeek/data_stream/known_certs/_dev/test/system/test-logs-config.yml
Show resolved
Hide resolved
packages/zeek/data_stream/known_hosts/_dev/test/system/test-logs-config.yml
Show resolved
Hide resolved
packages/zeek/data_stream/known_services/_dev/test/system/test-logs-config.yml
Show resolved
Hide resolved
packages/zeek/data_stream/software/_dev/test/system/test-logs-config.yml
Show resolved
Hide resolved
/test |
What does this PR do?
Add new data sets for known_hosts, known_certs, known_services, & software logs files.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots