Build stats

• Start Time: 2023-09-14T10:20:53.108+0000

• Duration: 243 min 51 sec

Test stats 🧪

> Show only the first 10 test failures

Check integrations / hashicorp_vault / hashicorp_vault: check / pipeline test: test-audit.log – hashicorp_vault.audit

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "access" is not one of the expected values (start, end, info) for any of the values of "event.category" (authentication)
[1] parsing field value failed: field "event.type" value "change" is not one of the expected values (start, end, info) for any of the values of "event.category" (authentication) 

Check integrations / hashicorp_vault / hashicorp_vault: check / pipeline test: test-faked-all-fields.log – hashicorp_vault.audit

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "access" is not one of the expected values (start, end, info) for any of the values of "event.category" (authentication)
[1] parsing field value failed: field "event.type" value "change" is not one of the expected values (start, end, info) for any of the values of "event.category" (authentication) 

Check integrations / slack / slack: check / system test: default – slack.audit

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in documents stored in logs-slack.audit-ep data stream: [0] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (access, change, creation, deletion, info) for any of the values of "event.category" (file) 

Check integrations / ti_rapid7_threat_command / ti_rapid7_threat_command: check / pipeline test: test-vulnerability-event.json – ti_rapid7_threat_command.vulnerability

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "info" is not one of the expected values (indicator) for any of the values of "event.category" (threat) 

Check integrations / pfsense / pfsense: check / pipeline test: test-pfsense-haproxy.log – pfsense.log

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "connection" is not one of the expected values (access, error, info) for any of the values of "event.category" (web) 

Check integrations / pfsense / pfsense: check / pipeline test: test-pfsense-openvpn.log – pfsense.log

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "error" is not one of the expected values (access, allowed, connection, denied, end, info, protocol, start) for any of the values of "event.category" (network)
[1] parsing field value failed: field "event.type" value "error" is not one of the expected values (start, end, info, access, allowed, connection, denied, protocol) for any of the values of "event.category" (authentication, network) 

Check integrations / ping_one / ping_one: check / pipeline test: test-pipeline-audit.log – ping_one.audit

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (admin, change, creation, deletion, group, info, user, access) for any of the values of "event.category" (iam, configuration) 

Check integrations / microsoft_defender_endpoint / microsoft_defender_endpoint: check / pipeline test: test-defenderatp.log – microsoft_defender_endpoint.log

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "creation" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (host, process)
[1] parsing field value failed: field "event.type" value "user" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (host) 

Check integrations / box_events / box_events: check / pipeline test: test-event-types.log – box_events.events

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "access" is not one of the expected values (start, end, info) for any of the values of "event.category" (authentication)
[1] parsing field value failed: field "event.type" value "admin" is not one of the expected values (access, change, creation, deletion, info) for any of the values of "event.category" (configuration)
[2] parsing field value failed: field "event.type" value "admin" is not one of the expected values (indicator, access, change, end, info, start) for any of the values of "event.category" (threat, process)
[3] parsing field value failed: field "event.type" value "admin" is not one of the expected values (start, end, info) for any of the values of "event.category" (session)
[4] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (access, change, creation, deletion, info) for any of the values of "event.category" (configuration)
[5] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (host)
[6] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (host, session)
[7] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (process)
[8] parsing field value failed: field "event.type" value "connection" is not one of the expected values (access, change, end, info, start, indicator) for any of the values of "event.category" (process, threat)
[9] parsing field value failed: field "event.type" value "creation" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (process)
[10] parsing field value failed: field "event.type" value "creation" is not one of the expected values (access, change, end, info, start, error) for any of the values of "event.category" (process, database)
[11] parsing field value failed: field "event.type" value "creation" is not one of the expected values (access, change, info, error) for any of the values of "event.category" (database)
[12] parsing field value failed: field "event.type" value "creation" is not one of the expected values (access, change, info, error, end, start) for any of the values of "event.category" (database, process)
[13] parsing field value failed: field "event.type" value "deletion" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (host)
[14] parsing field value failed: field "event.type" value "deletion" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (host, session)
[15] parsing field value failed: field "event.type" value "deletion" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (process)
[16] parsing field value failed: field "event.type" value "deletion" is not one of the expected values (access, change, end, info, start, error) for any of the values of "event.category" (process, database)
[17] parsing field value failed: field "event.type" value "deletion" is not one of the expected values (access, change, info, error) for any of the values of "event.category" (database)
[18] parsing field value failed: field "event.type" value "denied" is not one of the expected values (access, change, creation, deletion, info) for any of the values of "event.category" (configuration)
[19] parsing field value failed: field "event.type" value "denied" is not one of the expected values (access, change, end, info, start) for any of the values of "event.category" (process)
[20] parsing field value failed: field "event.type" value "denied" is not one of the expected values (access, change, end, info, start, admin, creation, deletion, group, user) for any of the values of "event.category" (process, iam)
[21] parsing field value failed: field "event.type" value "denied" is not one of the expected values (admin, change, creation, deletion, group, info, user, indicator) for any of the values of "event.category" (iam, threat)
[22] parsing field value failed: field "event.type" value "denied" is not one of the expected values (indicator, access, change, end, info, start) for any of the values of "event.category" (threat, process)
[23] parsing field value failed: field "event.type" value "denied" is not one of the expected values (start, end, info, indicator) for any of the values of "event.category" (authentication, threat)
[24] parsing field value failed: field "event.type" value "user" is not one of the expected values (access, change, end, info, start, error) for any of the values of "event.category" (process, database) 

Check integrations / proofpoint_tap / proofpoint_tap: check / pipeline test: test-clicks-permitted.log – proofpoint_tap.clicks_permitted

Expand to view the error details

 null 

Expand to view the stacktrace

 test case failed: one or more problems with fields found in documents: [0] parsing field value failed: field "event.type" value "allowed" is not one of the expected values (info) for any of the values of "event.category" (email) 

Show only the first 10 steps failures

Test integration: okta

• Took 0 min 28 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: pfsense

• Took 0 min 24 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: ping_one

• Took 0 min 19 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: prometheus_input

• Took 12 min 48 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: proofpoint_tap

• Took 1 min 34 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: slack

• Took 2 min 3 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: tenable_sc

• Took 0 min 30 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: ti_rapid7_threat_command

• Took 0 min 15 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: websphere_application_server

• Took 12 min 33 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Google Storage Download

• Took 0 min 0 sec . View more details here

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.